Porting to OS/2: aout vs omf
On OS/2, gcc supports two object formats. One is aout, which is a traditional format of Unix world. The other is OMF, which is a native format of OS/2. When porting to OS/2, which is more proper ? My answer is aout. Because aout is supported by binutils, which is used by most of projects from Unix world. Using OMF requires additional works. And aout can be converted to OMF easily with emxomf.exe. As well as, kLIBC/gcc supports aout to OMF auto-conversion at linking time. Whereas, OMF to aout is not supported. If you want to port, use aout. And if you develop a library with gcc, then use aout and convert it to OMF with emxomf.exe. How can I select aout or OMF ? gcc provides -Zomf flags. This flag unlike the other -Z flags, works as both a compilation flag and a linker flag. If -Zomf is used at compilation time, the object file is OMF format. Otherwise aout format. If -Zomf is used at linking time, OMF linkers by emxomfld.exe are used. Otherwise, ld.exe is used. By the way, I rec...