For reference, here is my vanilla BCC build script to build core + all contribs. Nothing else is needed, and I have no Harbour or C compiler parts in any default PATH, LIB, INSTALL or other envvars, so this should work on a _freshly installed system_ with BCC55 installed, and the Harbour sources (plus the 3rd party tools of course, which are *all optional*).
--- set PATH=C:\devl\bcc55\bin rem ; _optional_ 3rd party packages: set HB_DIR_ADS=C:\devl\ADS910\ACESDK set HB_DIR_ALLEGRO=C:\devl\allegro-4.2.2 set HB_DIR_APOLLO=C:\devl\Apollo-6.1.0.4 set HB_DIR_CURL=C:\devl\curl-7.19.3 set HB_DIR_FIREBIRD=C:\devl\Firebird-2.1.1 set HB_DIR_FREEIMAGE=C:\devl\FreeImage-3.11.0 set HB_DIR_GD=C:\devl\gd-2.0.34 set HB_DIR_LIBHARU=C:\devl\libharu-2.1.0 set HB_DIR_MYSQL=C:\devl\mysql-5.0.67 set HB_DIR_OPENSSL=C:\devl\openssl-0.9.8j set HB_DIR_PGSQL=C:\devl\pgsql-8.3.3 call make_b32.bat clean call make_b32.bat call make_b32.bat install cd contrib call make_b32_all.bat clean call make_b32_all.bat call make_b32_all.bat install cd .. --- And here is C:\devl\BCC55\Bin\bcc32.cfg: --- -I"C:\devl\BCC55\include" -L"C:\devl\BCC55\lib" --- Brgds, Viktor On Wed, Feb 11, 2009 at 3:24 PM, Przemyslaw Czerpak <[email protected]>wrote: > On Wed, 11 Feb 2009, Massimo Belgrano wrote: > > > 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. > > I use only bcc path common harbour and an old xharbour are in > > different directory with different lib > > Using harbour and xharbour i must have double bcc installed? > > No Massimo, you do not need it. > Just simply you created the problem _YOURSELF_ by adding xharbour > paths to BCC *.cfg files. It's not necessary for using xHarbour > and never was. Just remove it and create two separated batch files > with Harbour and xHarbour environment settings. > The main problem with environment variables is that 90% of users and > even [x]Harbour developers does not exactly know what they do but > they've seen them somewhere added to own build scripts and public the > final results on [x]Harbour related forums increasing the noise. > F.e. Enrico still keeps HB_LEX=simplex for xHarbour builds and this > variables is not necessary for xHarbour and AFAIR never was (maybe > only in 1-st few days of xHarbour life just after coping Harbour source) > because xHarbour has only one lexer and only this lexer can be and always > is enabled. Using HB_LEX may only exploit some bugs in old Harbour scripts > if they were not updated properly for xHarbour > In xMate default configuration there are macros which does not have any > effect or may cause that wrong binaries will be created. They also should > be removed. > In fact only few macros many times public here are used to compile Harbour > core code and in practice non of them is necessary to compile user code > by Harbour and/or C compiler. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
