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 )

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 )

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?

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
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?

5) a way to define default GTs. If no -gt is requested hbmk and hblnk
should use the ones defined at Harbour build time.

Any comment?

best regards,
Lorenzo
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to