So I insist to follow:
> ... most of OS/2 projects style using .obj and .lib in OMF
For sure Viktor can solve problem to use object extension in hbmk2.prg
I could sure spend a few hours on it, but 1) I don't
have time for it now 2) This would create an
unprecedented exception for gccomf, which I don't think
is a good idea on the long run (it has to be maintained).
+1) Since this is not the default in GCC, I assume they
had a good reason to make this decision, and any
3rd party tool is better not reinvent the wheel
since it may just cause problems down the road.
Once GCC OS/2 porters decide to switch to other
extension, we can follow suit.
At last we know that use of object extension in hbmk2.prg is not
important IF object file is an intermediate file which is deleted
after use
I just pointed lack of sync of file extension between phases, so in
current state hbmk2.exe does not work for os2gcc in OMF type
The idea is to use as few forced stuff and special
tricks as possible. On some occasions gcc -o _is_ used
even now, but only if inevitable (in -inc mode f.e.).
hbmk2 can use default .o for object files and .lib for library files
in OMF type without problems, but in my scripts I will continue
using .obj and .lib as usual in OS/2-OMF
If .o/.a is unusual for OS/2-OMF, the best place to
complain is GCC OS/2 developers.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
