On Wed, 04 Nov 2009, David Arturo Macias Corona wrote: Hi,
> And yes, you can use .o as object extension in OMF too, but try to > follow most of OS/2 projects style using .obj and .lib in OMF .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. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
