3 ms·
Can you say a bit more about the libraries?
by trasz 5y ago
Can you say a bit more about the libraries?
- pjmlp 5y agoEasy, just like Windows nowadays, because Aix uses COFF not ELF, and you also get private by default and description files listing which symbols are public. https://www.ibm.com/docs/en/xl-c-and-cpp-aix/16.1?topic=library-compiling-shared https://www.ibm.com/docs/en/xl-c-and-cpp-aix/16.1?topic=libr... CreateExportList is somehow similar to creating an import library in Windows, https://www.ibm.com/docs/en/xl-c-and-cpp-aix/16.1?topic=library-exporting-symbols-createexportlist-utility https://www.ibm.com/docs/en/xl-c-and-cpp-aix/16.1?topic=libr... Here are all details, https://download.boulder.ibm.com/ibmdl/pub/software/dw/aix/es-aix_ll.pdf https://download.boulder.ibm.com/ibmdl/pub/software/dw/aix/e...
- rjsw 5y agoAT&T SysV UNIX used COFF and had a similar process for creating shared libraries, don't think you can claim that it is not UNIX-style.
- pjmlp 5y agoMight be, but when I came to Aix 5, all other UNIXes used ELF so I never used that classical version. In fact, I never created shared libraries in either Xenix or DG/UX, and my first Linux was with kernel 1.0.9, where ELF was introduced. So thanks for the correction.
- inkyoto 5y agoAIX introduced an extended COFF object and executable file format, XCOFF, that has eliminated the need to have both, static and shared, library files – the .a files were «both» at once and the linker switch had to be used to select between a statically or dynamically linked executable type. Which caused a lot of confusion for some at the time leading them to believe that AIX had no shared libraries.