Przemek:
>.a is not library extension. It's extension used by archive files
>created by 'ar' program. It doesn't matter what files you will
>store inside.
>As long we are using 'ar' to create archives with set of object files
>then such archives should use .a extension or we only confuse other
>programs which recognize file type using extension in file name.
>If we are using different program to create set of objects which
>can be used as library by linker then we should also use it's native
>extension and if they use .lib we should not change it anyhow it
>may badly interact with some GCC extensions, i.e. -l<libname> may
>stop to work so such things should be checked first.
>To not confuse users for object files we should use the same extension
>as OMF GCC uses by default when -c option is used.
Again I suggest to follow:
> ... most of OS/2 projects style using .obj and .lib in OMF
We are not using ar.exe but emxomfar.exe in OMF
As explained, "gcc -c" use .o as native extension because it came from
old gcc port to OS/2 when only a.out type was available
I checked variations of next code:
---------------------
harbour.exe -n2 test.prg -i..\..\..\include
Rem .c compile phase
gcc.exe -o test.obj -c -O3 -DTCPV40HDRS -DHB_FM_STATISTICS_OFF -Wall -W
-Zomf -I..\..\..\include test.c
Rem linking phase
gcc.exe test.obj -Le:\usr\lib\tcpipv4 -Zomf -lhbextern -lhbdebug -lhbvm
-lhbrtl -lhblang -lhbcpage -lgtcgi -lgtpca -lgtstd -lgtos2 -lhbrdd
-lhbuddall -lhbusrrdd -lrddntx -lrddcdx -lrddnsx -lrddfpt -lhbrdd
-lhbhsx -lhbsix -lhbrtl -lhbvm -lhbmacro -lhbcplr -lhbpp -lhbcommon
-lsocket -o test.exe -L..\..\..\lib\os2\gccomf
---------------------
It work using:
a) "-o test.obj" in .c compile phase
"test.obj" in linking phase
b) without "-o" in .c compile phase
"test.o" in linking phase
c) Surprise :-)
I renamed all .lib files to .a files in lib\os2\gccomf
There are no .lib files available
Linking work without problem
It show that "-l<libname>" search for either .a or .lib files
d) I renamed hbrtl.a to hbrtl.lib and rest remain as .a files
Linking work without problem
Again "-l<libname>" search for either .a or .lib files
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
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
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
David Macias
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
