Thanks Alex, I forgot about these details.
> They do different things although they are symlinks: > > "xhbcc" is a wrapper to the harbour compiler only. It only sets environment > variables. The result of its work is a C file. I'll add support for this, by hbmk switch '-cc'. so hbcc script shall be: 'hbmk -cc $*' > Use "xhbcmp" exactly as you would use the harbour compiler itself. > The main difference with xhbcmp is that it results in an object file, > not a C file that needs compiling down to an object. xhbcmp also > ensures that the harbour include directory is seen by the harbour compiler. I'll add support for this too, by hbmk switch '-cmp'. so hbcmp script shall be: 'hbmk -cmp $*' > "xhblnk" simply takes a list of object files and links them together > with the harbour virtual machine and run-time library to produce an > executable. The executable will be given the basename of the first object > file if not directly set by the "-o" command line switch. Given that hbmk already accepts a pure list obj objects, this doesn't need a separate switch. hbmk will now consider obj filename too as executable name, if found before other input files. > "xhbmk" tries to produce an executable from your .prg file. It's a simple > equivalent of cl.bat from the CA-Clipper distribution. Default mode of hbmk. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
