The information provided by Hammer is excellent and worth noting and applying.
There is one other thing you should be aware of if you intend to compile win32 api programs on winNT/9x: you should add the following macro definitions to your bcc32.cfg file:
Code:
-DWINVER=0x0400
-D_WIN32_WINNT=0x0400
This is because the cmd line tools are setup for win2k by default. While your programs may compile ok without these macro definitions you will find that occasionally your programs will not run as expected. An example of this occurs when using common dialogs; the common dialog you are attempting to invoke will not appear under win9x unless you have defined these macros.
You may also wish to include the path to the psdk files in both configuration files if you intend to code with win32 api.
Example bcc32.cfg file for winNT/9x
Code:
-DWINVER=0x0400
-D_WIN32_WINNT=0x0400
-I"c:\Borland\Bcc55\include"
-L"c:\Borland\Bcc55\lib;c:\Borland\Bcc55\lib\psdk"
Example bcc32.cfg file for win2k/xp
Code:
-I"c:\Borland\Bcc55\include"
-L"c:\Borland\Bcc55\lib;c:\Borland\Bcc55\lib\psdk"
Example ilink.cfg file for all windows os
Code:
-L"c:\Borland\Bcc55\lib;c:\Borland\Bcc55\lib\psdk"
Remember to save the two configuration files (bcc32.cfg, ilink32.cfg) in the bin directory of your Borland command line tools installation. Also remember to change the paths in these configuration files to that of your actual command line tools installation, if necessary.