2023-12-25 22:01 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Now I get this:
***For your convenience xHarbour's bin directory was added to your PATH
For your convenience MSVC's bin folders were added to PATH
Removing System and Object Files ...
Removing DLL and Object Files ...
Removing Contrib Libraries and Object Files ...
Done ...
****** End of Job *****
***For your convenience xHarbour's bin directory was added to your PATH
For your convenience MSVC's bin folders were added to PATH
Creating System Files (ST) ...
"nmake" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
"notepad" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
***For your convenience xHarbour's bin directory was added to your PATH
For your convenience MSVC's bin folders were added to PATH
Creating Contrib Libraries ...
"nmake" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
"notepad" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
Premere un tasto per continuare . . .
The idea behind the make and build scrips is to allow users to build
their applications (and xHarbour if they choose) withOUT having to
set anything, other than STANDARD installation of their C
compiler[s].
As per the ChangeLog we now have a unified find_vc.bat and
find_bc.bat - Your errors above suggest that you have MSVC and BCC in locations NOT detected by find_vc.bat/find_bc.bat.
Can you please advise me which Version of MSVC you have and WHICH
Directory it was installed into, was it the standard default install location?
Can you please provide same info for your BCC installation?
If you have NON STANDARD install, what was your past approach? Did
you add your BCC to PATH and just called make_bc.bat? If so I will
quickly add support for that approach.
Il 26/12/2023 16:16, Ron Pinkas ha scritto:
The idea behind the make and build scrips is to allow users to build
their applications (and xHarbour if they choose) withOUT having to
set anything, other than STANDARD installation of their C
compiler[s].
As per the ChangeLog we now have a unified find_vc.bat and find_bc.bat - Your errors above suggest that you have MSVC and BCC in
locations NOT detected by find_vc.bat/find_bc.bat.
Can you please advise me which Version of MSVC you have and WHICH
Directory it was installed into, was it the standard default install location?
Can you please provide same info for your BCC installation?
I have more than one version installed of MSC and BCC, so I can't have
them all in the standard default install location.
If you have NON STANDARD install, what was your past approach? Did you
add your BCC to PATH and just called make_bc.bat? If so I will
quickly add support for that approach.
My approach for years is:
SET CC_DIR=<installation directory>
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 14:02:00 |
| Calls: | 12,101 |
| Calls today: | 1 |
| Files: | 15,004 |
| Messages: | 6,518,017 |