On Sun, 04 May 2008, Lorenzo Fiorini wrote: Hi Lorenzo,
> What I'm trying to achieve is to use hb* scripts inside gnu make > makefiles to minimize differences between Linux, MacOSX and Windows. > I've rebuilt Linux makefiles using only hb* scripts but when I've used > them under msys/mingw ( in short win ) I've found some small > differences. For every one there is a solution but I think it would be > good if we try to the things as easy as possible. > 1) in win hbmk -ofirst.exe first.prg > creates first.exe.exe unlike hbcc -ofirst.exe first.c which creates > first.exe and hb-mkslib libxyz.dll which create libxyz.dll ( not > libxyz.dll.dll ) It should be fixed. I'll do that. > 2) hbmk -ofirst first1.prg creates and delete an intermediate C file > called first.c that for example deletes the source of the C example > above ( for this I've noted it ) Yes. I know about it. Anyhow simple call to harbour first.prg will also overwrite the first.c file so I decided to not touch it. Though in the past I lost some files in such way. > 3) in Linux hb-mkslib libxyz libxyz.a creates a libxyz.so while in win > it require to add harbour.dll to the command line. Could hb-mkslib > take care of this? This is not such simple. In MS-Windows harbour.dll is required because linker needs to know all dependeces when creates new .dll In Linux there is no such limitation. hb-mkslib can be used also for libraries which do not use HVM API and in such case harbour.dll will not be required so forcing it will introduce unnecessary limitation. I'll look at it but I cannot promise that I'll find nice solution. Please also remember that in Windows the same will be necessary for any other libraries your code will use not only for harbour.dll. > 4) a way to manage contribs in hb* scripts > f.e. for me hbgd,hbpgsql,hbct,hbzlib are "standard" libs and I've to > provide the necessary dependences at Harbour build time, but after I'll add most of contrib libraries to hb* scripts. > that I've to include in all the makefiles the same infos > -L/lib/path/to/xyz -lhbxyz -lxyz. Could hbmk, hb-mkslib "store" the > references of the "extensions" added at build time and add them to the > -Iincludes -Llibpaths -llibs? See: CC_C_USR and CC_L_USR > 5) a way to define default GTs. If no -gt is requested hbmk and hblnk > should use the ones defined at Harbour build time. And they do that. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
