On Wed, 11 Feb 2009, Massimo Belgrano wrote: > For compile harbour and contrib with bcc i set this env after set path > SET HB_ARCHITECTURE=WIN > SET HB_COMPILER=bcc32 > SET INCLUDE=c:\harbour\INCLUDE;c:\xharbour\bcc55\INCLUDE;c:\oohg\include; > SET LIB=c:\harbour\LIB;c:\xharbour\bcc55\lib;c:\xharbour\bcc55\lib\PSDK > SET HB_PATH=c:\harbour > SET HB_BIN_INSTALL=c:\harbour\BIN > SET HB_LIB_INSTALL=c:\harbour\LIB > SET HB_INC_INSTALL=c:\harbour\INCLUDE > SET L_USR= > SET PRG_USR=-l > SET C_USR=-DHB_FM_STATISTICS_OFF -tWM -OS -Ov -Oi -Oc -Q > SET HB_BUILD_ST=
L_USR and PRG_USR are not longer used. > SET INCLUDE=c:\harbour\INCLUDE;c:\xharbour\bcc55\INCLUDE;c:\oohg\include; > in bcc32.cfg > -I"c:\Xharbour\bcc55\include" > -L"c:\xharbour\bcc55\lib" > -L"C:\xharbour\BCC55\Lib\PSDK" > in ilink32.cfg > -L"c:\xharbour\bcc55\lib" > -L"C:\xharbour\BCC55\Lib\PSDK" > I share bcc with xharbour The above is very bad idea. It sets access to Harbour and xHarbour header files simultaneously. They are not binary compatible so you will create wrong binaries at least for one of the above compilers. _NEVER_ _MIX_ INCLUDE, BIN, and LIB paths for both compilers because many files have exactly the same name. As result you may have unpredictable compile time or runtime errors. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
