On Tue, 03 Mar 2009, Szak�ts Viktor wrote: Hi,
> I've checked the source of hbmk script and hbmk2 was right the first time, so > I will change it back, but in this case I don't understand point 1. and 2. > of your bug report. I was looking for the form to create t1.o file from t1.prg and t2.o file from t2.c so I tried different combinations to check what hbmk2 does. Any of them made what I needed. That's all. > BTW, why hbcc for Harbour compiler? 'hbcc' seems to imply "Harbour > C Compiler", while 'hbcmp' seems to mean 'Harbour Compiler'. > What are the reasons behind the names? Exactly the same as in doc/howtobld.txt: "hbcc" is a wrapper to the C compiler only. It sets all flags and paths necessary to compile .c files which include Harbour header files. The result of its work is an object file. Use "hbcmp" exactly as you would use the harbour compiler itself. The main difference with hbcmp is that it results in an object file, not a C file that needs compiling down to an object. hbcmp also ensures that the harbour include directory is seen by the harbour compiler. "hblnk" 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. hbcc as script cannot be used for .prg files so here you can extend it and add such support generating .c file as result of Harbour compiler execution but this will be an hbmk2 extension. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
