2023-12-26 17:07 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* make_bc.bat
* make_vc.bat
+ bin/find_bc.bat
+ bin/find_vc.bat
* More refinments and support for User defined CC_DIR or C Compiler in path.
Il 26/12/2023 23:09, Ron Pinkas ha scritto:
2023-12-26 17:07 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* make_bc.bat
* make_vc.bat
+ bin/find_bc.bat
+ bin/find_vc.bat
* More refinments and support for User defined CC_DIR or C Compiler in path.
Sorry, still does not work. :-(
"ERROR: Microsoft Visual C++ not found!"
---------------------------------------
Make Utility for Miscosoft Visual C/C++
---------------------------------------
Microsoft Visual C/C++ not found.
Please install Microsoft Visual C/C++ and try again.
"ERROR: Microsoft Visual C++ not found!"
---------------------------------------
Make Utility for Miscosoft Visual C/C++
---------------------------------------
Microsoft Visual C/C++ not found.
Please install Microsoft Visual C/C++ and try again.
"ERROR: Microsoft Visual C++ not found!"
---------------------------------------
Make Utility for Miscosoft Visual C/C++
---------------------------------------
Microsoft Visual C/C++ not found.
Please install Microsoft Visual C/C++ and try again.
Please provide exact steps from a FRESH cmd.exe terminal.
I am also curious why you the message 3 times.
Il 26/12/2023 23:33, Ron Pinkas ha scritto:
Please provide exact steps from a FRESH cmd.exe terminal.
I am also curious why you the message 3 times.
My cmd.exe is always fresh. I don't use the same cmd.exe for different compilers. I get the message 3 times because in my batch I have:
CALL make_vc clean
CALL make_vc core
CALL make_vc contrib
With:
make_vc all
I get a single error message.
Cool, since you don't specify CC_DIR (good), it must tbe auto dettected
and we simply don't yet have your MSVC Location added to find_vc.bat.
Please let me know WHERE is your MSVC insttalled so I can add it.
Il 26/12/2023 23:46, Ron Pinkas ha scritto:
Cool, since you don't specify CC_DIR (good), it must tbe auto dettected
and we simply don't yet have your MSVC Location added to find_vc.bat. Please let me know WHERE is your MSVC insttalled so I can add it.
Ron, if you don't want to fix it, I can do it, no problem. I always
specify CC_DIR. The problem seems to be in find_vc.bat. It cannot be so difficult to fix it. Are you willing to do it or not?
Justt tell me YOUR STEPS including YOUR CC_DIR and I will fix it. Of
course I want and will fix it, as soon as you are willing to share
YOUR EXACT STEPS, please.
Il 26/12/2023 23:58, Ron Pinkas ha scritto:
Justt tell me YOUR STEPS including YOUR CC_DIR and I will fix it. Of
course I want and will fix it, as soon as you are willing to share
YOUR EXACT STEPS, please.
These are my steps:
SET MSC=e:\msc32\msc
SET CC_DIR=%MSC%
SET INCLUDE=%MSC%\include\ucrt;%MSC%\include;%MSC%\include\sdk
SET LIB=%MSC%\lib;%MSC%\lib\sdk
make_vc all
...
These are my steps:
SET MSC=e:\msc32\msc
SET CC_DIR=%MSC%
SET INCLUDE=%MSC%\include\ucrt;%MSC%\include;%MSC%\include\sdk
SET LIB=%MSC%\lib;%MSC%\lib\sdk
make_vc all
Thanks, It might be fixed after:
2023-12-26 19:18 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Please advise. and sorry for the trouble butt I believe the new system
is far cleaner and superior - should worth the efforts in the long
term. :)
The problem is here:
cl > nul 2>&1 || GOTO NOT_FOUND
In that point we are in the root xHarbour directory so cl.exe could not
be found.
Sorry, no changes. :-(
Using CC_DIR: 'e:\msc32\msc'
"ERROR: Microsoft Visual C++ not found!"
---------------------------------------
Make Utility for Miscosoft Visual C/C++
---------------------------------------
Microsoft Visual C/C++ not found.
Please install Microsoft Visual C/C++ and try again.
It works if I add this to find_vc.bat:
SET PATH=%CC_DIR%\bin
cl > nul 2>&1 || GOTO NOT_FOUND
Unfortunately this is not working (BCC32):
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Il 27/12/2023 12:13, Enrico Maria Giordano ha scritto:
Unfortunately this is not working (BCC32):
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
It works in this form:
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET BCC_LIB=%BCC%\lib;%BCC%\lib\psdk
REM SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Maybe makefile.bc needs to be cleaned up.
Unfortunately this is not working (BCC32):
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Was it working like that before my changes? AFAIK I did not touch LFLAGS support.
It works in this form:
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET BCC_LIB=%BCC%\lib;%BCC%\lib\psdk
REM SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Maybe makefile.bc needs to be cleaned up.
In the above settup LFLAGS is redundant since BCC_LIB is enough.
FWIW if you have correctt .cfg file next to your bcc32.exe or bcc32c.exe
then even BCC_LIB is not needed because it is auto built from the .cfg
file.
Il 27/12/2023 18:25, Ron Pinkas ha scritto:
Unfortunately this is not working (BCC32):
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Was it working like that before my changes? AFAIK I did not touch LFLAGS support.
Yes, of course, it was working. I can search the bug, if you want me to.
It works in this form:
@ ECHO OFF
SET BCC=e:\bcc32\bcc
SET PATH=%BCC%\bin;%PATH%
SET CC_DIR=%BCC%
SET BCC_LIB=%BCC%\lib;%BCC%\lib\psdk
REM SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
CALL make_bc all
PAUSE
Maybe makefile.bc needs to be cleaned up.
In the above settup LFLAGS is redundant since BCC_LIB is enough.
So, the new form is with BCC_LIB instead of LFLAGS? Please confirm.
...
So, the new form is with BCC_LIB instead of LFLAGS? Please confirm.
I did NOT intentend to change LFLAGS support - So, IF it was working
before then it should still work correctly or we need to find what
changed. But, I believe that NITHER should be specified for correct BCC installation.
Il 27/12/2023 19:22, Enrico Maria Giordano ha scritto:
So, the new form is with BCC_LIB instead of LFLAGS? Please confirm.
I did NOT intentend to change LFLAGS support - So, IF it was working before then it should still work correctly or we need to find what changed. But, I believe that NITHER should be specified for correct BCC installation.
Ok, I will try to find the problem...
It seems to work fine with this addition in find_bc.bat, please confirm
it is the proper fix:
:DIR_SET
IF NOT EXIST "%CC_DIR%\bin\bcc32c.exe" IF NOT EXIST
"%CC_DIR%\bin\bcc32.exe" GOTO NOT_FOUND
IF "%CC%"=="" IF EXIST "%CC_DIR%\bin\bcc32c.exe" SET "CC=bcc32c"
IF "%CC%"=="" IF EXIST "%CC_DIR%\bin\bcc32.exe" SET "CC=bcc32"
REM Let's make sure the PATH is set correctly
make -h > nul 2>&1 || ECHO For your convenience BCC's bin directory was
added to your PATH && SET PATH=%CC_DIR%\bin;%PATH%
IF NOT "%BCC_LIB%"=="" GOTO FOUND
IF NOT "%LFLAGS%"=="" GOTO FOUND <-- THIS ADDITION!!!
So, the new form is with BCC_LIB instead of LFLAGS? Please confirm.
I did NOT intentend to change LFLAGS support - So, IF it was working
before then it should still work correctly or we need to find what
changed. But, I believe that NITHER should be specified for correct BCC
installation.
Ok, I will try to find the problem...
IF NOT "%LFLAGS%"=="" GOTO FOUND <-- THIS ADDITION!!!
Cool, thx, but I am confused, this simply SKIP over the logic to build BCC_LIB from the .cfg file - The .cfg logic does not touch LFLAGS so why
does it interfere with LFLAGS?
Il 28/12/2023 17:01, Ron Pinkas ha scritto:
IF NOT "%LFLAGS%"=="" GOTO FOUND <-- THIS ADDITION!!!
Cool, thx, but I am confused, this simply SKIP over the logic to build BCC_LIB from the .cfg file - The .cfg logic does not touch LFLAGS so why does it interfere with LFLAGS?
Because I have no -L in bcc32.cfg, as I'm using LFLAGS instead.
Because I have no -L in bcc32.cfg, as I'm using LFLAGS instead.
I understand, but the .cfg files does NOT erase your LFLAGS so it
should still work too, no?
Il 28/12/2023 19:54, Ron Pinkas ha scritto:
Because I have no -L in bcc32.cfg, as I'm using LFLAGS instead.
I understand, but the .cfg files does NOT erase your LFLAGS so it
should still work too, no?
No, because the script produces an empty -L switch:
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
No, because the script produces an empty -L switch:
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
Well then it should have had -$(LFLAGS) - did I remove it? If nt how did
it work before?
Il 29/12/2023 23:05, Ron Pinkas ha scritto:
No, because the script produces an empty -L switch:
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
Well then it should have had -$(LFLAGS) - did I remove it? If nt how did
it work before?
The culprit is this line:
LINK_CMD =$(LINKEXE) $(CC_LINKER_DEBUG_FLAGS) -ap -Tpe -x -Gn -C -L$(LIB_DIR) -L$(BCC_LIB) $(LFLAGS) $(BCC_STARTUP_OBJ) $**,$@,,
where -L$(BCC_LIB) is output as -LECHO disattivato. I still don't
understand why... Maybe because BCC_LIB is empty?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 133:44:03 |
| Calls: | 12,087 |
| Files: | 14,997 |
| Messages: | 6,517,349 |