This is what I get building xHarbour with MSC32 using the current
repository:
For your convenience xHarbour's bin directory was added to your PATH.
Could not find Microsoft C++ at 'e:\msc32\msc'!
There is no %CC_DIR%\Common7\Tools\VsDevCmd.bat in my MSC installation.
Why not testing for the existence of %CC_DIR%\bin\cl.exe instead?
Not instead, I will add it. The latest versionss of MSVC do not have a bin\cl.exe.
Il 04/01/2024 10:12, Enrico Maria Giordano ha scritto:
This is what I get building xHarbour with MSC32 using the current repository:
For your convenience xHarbour's bin directory was added to your PATH.
Could not find Microsoft C++ at 'e:\msc32\msc'!
The problem seems to be in these lines:
REM MSC Specific!
IF EXIST "%CC_DIR%\Common7\Tools\VsDevCmd.bat" EXIT /B 0
IF EXIST "%CC_DIR%\..\Common7\Tools\VsDevCmd.bat" EXIT /B 0
There is no %CC_DIR%\Common7\Tools\VsDevCmd.bat in my MSC installation.
Why not testing for the existence of %CC_DIR%\bin\cl.exe instead?
Il 04/01/2024 15:38, Ron Pinkas ha scritto:
There is no %CC_DIR%\Common7\Tools\VsDevCmd.bat in my MSC installation. Why not testing for the existence of %CC_DIR%\bin\cl.exe instead?
Not instead, I will add it. The latest versionss of MSVC do not have a bin\cl.exe.
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
For many many years MSVC is installed onto the locations you can see in known.vc file and those installations have a common7\Tools sub folder.
They also have multiple cl.exe like this:
Il 04/01/2024 15:38, Ron Pinkas ha scritto:
There is no %CC_DIR%\Common7\Tools\VsDevCmd.bat in my MSC installation. Why not testing for the existence of %CC_DIR%\bin\cl.exe instead?
Not instead, I will add it. The latest versionss of MSVC do not have a bin\cl.exe.
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
Il 04/01/2024 17:08, Ron Pinkas ha scritto:
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
For many many years MSVC is installed onto the locations you can see in known.vc file and those installations have a common7\Tools sub folder.
They also have multiple cl.exe like this:
Ok, but I never used the standard mess of MS, only the usual
bin/include/lib directories. Can you make the build system to work with
this too, please?
Il 04/01/2024 17:08, Ron Pinkas ha scritto:
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
For many many years MSVC is installed onto the locations you can see in known.vc file and those installations have a common7\Tools sub folder.
They also have multiple cl.exe like this:
Ok, but I never used the standard mess of MS, only the usual
bin/include/lib directories. Can you make the build system to work with
this too, please?
Enrico Maria Giordano wrote:
Il 04/01/2024 17:08, Ron Pinkas ha scritto:
Thank you. To what "latest version" are you referring to? Mine is
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
From which version there is no cl.exe anymore? And what is there instead?
For many many years MSVC is installed onto the locations you can see in known.vc file and those installations have a common7\Tools sub folder. They also have multiple cl.exe like this:
Ok, but I never used the standard mess of MS, only the usual bin/include/lib directories. Can you make the build system to work with this too, please?
Of course. :)
Ok, but I never used the standard mess of MS, only the usual
bin/include/lib directories. Can you make the build system to work with
this too, please?
Of course. :)
How did you do that, did you manually move it or was there an
installation option?
Please check after: 2024-01-04 12:50 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Il 04/01/2024 18:52, Ron Pinkas ha scritto:
Please check after: 2024-01-04 12:50 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Now I get this:
For your convenience xHarbour's bin directory was added to your PATH. Impossibile trovare il percorso specificato.
"ERROR: Microsoft C++ not found!"
---------------------------------------
Make Utility for Miscosoft Visual C/C++
---------------------------------------
Microsoft Visual C/C++ not found.
Please install and try again.
Sorry, try: 2024-01-04 13:21 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
BCC64, I get:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Could not find Borland C++ at 'e:\fw\temp\bcc64\bcc'!
Search known locations (Y/N)? y
Searching for Borland C++...
"ERROR: Borland C++ not found!"
------------------------------
Make Utility for Borland C/C++
------------------------------
Borland C/C++ not found.
Please install and try again.
My batch:
@ ECHO OFF
SET BCC=e:\fw\temp\bcc64\bcc
SET CC_DIR=%BCC%
SET HB_ARCH=64
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
BCC32 errors out:
ILINK32 -ap -Tpe -x -Gn -C -Llib\b32 -LECHO disattivato. -Le:\bcc32\bcc\lib;e:\bcc32\bcc\lib\psdk c0x32.obj obj\b32\hblib.obj ,bin\b32\hblib.exe,, ws2_32.lib cw32mt.lib import32.lib
Turbo Incremental Link 6.97 Copyright (c) 1997-2022 Embarcadero
Technologies, Inc.
Fatal: Unable to open file 'DISATTIVATO.'
My batch:
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET CC_DIR=%BCC%
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
BCC64, I get:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
e:\fw\temp\bcc64\bcc
I am going to review but few immediate notes for you:
1. HB_ARCH should be w64 - I know you reverted makegc64.bat but instead
the makefile for gcc should be corrected.
2. If the compiler has a <>.cfg file then you don't need to set LFLAGS.
I have no clue where '-LECHO disattivato.' comes from. I will have to try
to simulate your setup.
What is the name of the compiler executable in:
e:\fw\temp\bcc64\bcc\bin
BCC64, I get:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Are you sure you get that line duplicated? I am not able to replicate
nor can I explain.
Il 04/01/2024 20:46, Ron Pinkas ha scritto:
What is the name of the compiler executable in:
e:\fw\temp\bcc64\bcc\bin
bcc64.exe
Please note that it is a CLANG compiler.
Il 04/01/2024 20:44, Ron Pinkas ha scritto:
I have no clue where '-LECHO disattivato.' comes from. I will have to try to simulate your setup.
It comes from this line, I think:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) -L$(BCC_LIB) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
because BCC_LIB is empty.
Il 04/01/2024 20:51, Ron Pinkas ha scritto:
BCC64, I get:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Are you sure you get that line duplicated? I am not able to replicate
nor can I explain.
No, sorry, it is NOT duplicated.
Il 04/01/2024 20:39, Ron Pinkas ha scritto:
I am going to review but few immediate notes for you:
1. HB_ARCH should be w64 - I know you reverted makegc64.bat but instead
the makefile for gcc should be corrected.
Please, look at this line (just an example):
-lvm$(HB_MT)$(HB_ARCH)$(HB_DEBUG)
The library name should be:
vm64
But if HB_ARCH is w64 the name would be:
vmw64
that is not correct. So, how to fix it?
2. If the compiler has a <>.cfg file then you don't need to set LFLAGS.
Yes, I know, but I prefer using LFLAGS so I don't have to change the
content of the CFG file any time I rename the compiler installation directory.
Il 04/01/2024 20:46, Ron Pinkas ha scritto:
What is the name of the compiler executable in:
e:\fw\temp\bcc64\bcc\bin
bcc64.exe
Please note that it is a CLANG compiler.
Please, look at this line (just an example):
-lvm$(HB_MT)$(HB_ARCH)$(HB_DEBUG)
The library name should be:
vm64
But if HB_ARCH is w64 the name would be:
vmw64
that is not correct. So, how to fix it?
Enrico, I am not arguing just curious, why would vmw64 be a wrong name?
2. If the compiler has a <>.cfg file then you don't need to set LFLAGS.
Yes, I know, but I prefer using LFLAGS so I don't have to change the
content of the CFG file any time I rename the compiler installation
directory.
Now you have me real curious :) - WHY/WHEN do you need to rename?
bcc64.exe
Please note that it is a CLANG compiler.
Is that the original name in the official distribution or do they have bcc64c.exe and bcc664x.exe?
Il 04/01/2024 21:23, Ron Pinkas ha scritto:
bcc64.exe
Please note that it is a CLANG compiler.
Is that the original name in the official distribution or do they have bcc64c.exe and bcc664x.exe?
No, BCC64 only comes in CLANG flavour.
Il 04/01/2024 21:26, Ron Pinkas ha scritto:
Please, look at this line (just an example):
-lvm$(HB_MT)$(HB_ARCH)$(HB_DEBUG)
The library name should be:
vm64
But if HB_ARCH is w64 the name would be:
vmw64
that is not correct. So, how to fix it?
Enrico, I am not arguing just curious, why would vmw64 be a wrong name?
I don't know... because the one for MSC64 is called vm64.lib? Are you proposing to change the name for MGW64 to vmw64.lib? If yes, why?
2. If the compiler has a <>.cfg file then you don't need to set LFLAGS.
Yes, I know, but I prefer using LFLAGS so I don't have to change the content of the CFG file any time I rename the compiler installation directory.
Now you have me real curious :) - WHY/WHEN do you need to rename?
I experiment with different compiler versions so I need to change their location often. I don't want to change the CFG file any time.
Enrico, if you add:
SET CC=bcc64
Does it fix the problem?
I experiment with different compiler versions so I need to change their
location often. I don't want to change the CFG file any time.
But you can have as many compilers as you want and each in its own
(properly named) directory - what am I missing?
I have no clue where '-LECHO disattivato.' comes from. I will have to try
to simulate your setup.
It comes from this line, I think:
LINK_CMDÂ Â Â Â Â Â =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) -L$(BCC_LIB) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
because BCC_LIB is empty.
Il 04/01/2024 23:07, Ron Pinkas ha scritto:
I experiment with different compiler versions so I need to change their location often. I don't want to change the CFG file any time.
But you can have as many compilers as you want and each in its own (properly named) directory - what am I missing?
If I move one compiler from a directory to another then I had to change
the CFG.
Il 04/01/2024 21:30, Ron Pinkas ha scritto:
because BCC_LIB is empty.
But if its empty it shold just have been '-L' (empty) - so strange.
Do you want me to find the bug?
Il 04/01/2024 21:17, Enrico Maria Giordano ha scritto:
I have no clue where '-LECHO disattivato.' comes from. I will have to try to simulate your setup.
It comes from this line, I think:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) -L$(BCC_LIB) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
because BCC_LIB is empty.
If I remove -L$(BCC_LIB) then it works fine:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
Il 04/01/2024 21:46, Ron Pinkas ha scritto:
Enrico, if you add:
SET CC=bcc64
Does it fix the problem?
No:
For your convenience xHarbour's bin directory was added to your PATH.
'bcc64' is not supported by this batch file.
------------------------------
Make Utility for Borland C/C++
------------------------------
Borland C/C++ not found.
Please install and try again.
My batch:
@ ECHO OFF
SET BCC=e:\fw\temp\bcc64\bcc
SET CC_DIR=%BCC%
SET CC=bcc64
SET HB_ARCH=64
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Il 04/01/2024 21:46, Ron Pinkas ha scritto:
Enrico, if you add:
SET CC=bcc64
Does it fix the problem?
No:
For your convenience xHarbour's bin directory was added to your PATH.
'bcc64' is not supported by this batch file.
------------------------------
Make Utility for Borland C/C++
------------------------------
Borland C/C++ not found.
Please install and try again.
My batch:
@ ECHO OFF
SET BCC=e:\fw\temp\bcc64\bcc
SET CC_DIR=%BCC%
SET CC=bcc64
SET HB_ARCH=64
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Enrico Maria Giordano wrote:
Il 04/01/2024 21:17, Enrico Maria Giordano ha scritto:
I have no clue where '-LECHO disattivato.' comes from. I will have to try
to simulate your setup.
It comes from this line, I think:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) -L$(BCC_LIB) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
because BCC_LIB is empty.
If I remove -L$(BCC_LIB) then it works fine:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
its simple to fix using bcclibflag tthat will be empty if bcc_lib is
empty.
If I remove -L$(BCC_LIB) then it works fine:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C
-L$(LIB_DIR) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
its simple to fix using bcclibflag tthat will be empty if bcc_lib is
empty.
If I move one compiler from a directory to another then I had to change
the CFG.
But why move? you can have all the compilers, each one in itts own fixed location, no?
Should be fixed after: 2024-01-04 19:36 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Il 05/01/2024 00:22, Ron Pinkas ha scritto:
If I remove -L$(BCC_LIB) then it works fine:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
its simple to fix using bcclibflag tthat will be empty if bcc_lib is
empty.
I don't understand. Can you apply the fix yourself so I can test it, please?
I don't understand. Can you apply the fix yourself so I can test it, please?
I did, and did describe itt in the ChanngeLog.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 399 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 67:08:12 |
| Calls: | 8,355 |
| Calls today: | 15 |
| Files: | 13,159 |
| Messages: | 5,894,225 |
| Posted today: | 1 |