> > Audodetect is based on search of compiler in path?
No, first it checks the dir where the executed hbmk executable is located. If it finds a harbour executable there, it assumes a regular binary install with root/bin, root/include, root/lib structure. Then it looks a few directory level upper, for those cases where hbmk exe is copied into subdirs, but this is just for mere convenience. Some regular Linux install paths (/opt/harbour/ and /usr/local/bin/ currently) are also detected and inc/lib dirs adjusted accordingly. If someone knows other standard *nix paths where Harbour is installed, please tell, and I'll add it. > better way if will possible is set path of your c compiler as only > works and call a compilation batch that like hbmk2 show the detected > compiler and go C compiler is detected from PATH. But this doesn't work well on *nix systems, so it's only used on win/dos/os2. > Is still required bison? > must SET BISON_SIMPLES ? No, it's not required at all for hbmk. It's not even needed to build Harbour, since long. You can forget about it. (unless you want to tweak the Harbour grammar parser) Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
