vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Can anyone explain me the library naming convention in AIX. The library libicuio.so is named in linux as: libicuio.so, libicuio.so.34 and libicuio.so.34.0. While in AIX it is named as: libicuio.a, libicuio34.a and libicuio34.0.a. Does it mean that we have to name libraries in AIX as: libicu<MAJOR_VERSION>.<MINOR_VERSION>.a |
| |||
| smiletolead wrote: > Can anyone explain me the library naming convention in AIX. The library > libicuio.so is named in linux as: libicuio.so, libicuio.so.34 and > libicuio.so.34.0. > While in AIX it is named as: libicuio.a, libicuio34.a and > libicuio34.0.a. Does it mean that we have to name libraries in AIX as: > libicu<MAJOR_VERSION>.<MINOR_VERSION>.a > You can use Unix/Linux convention and have libfoo.2.3.so with libfoo.2.so and libfoo.so (symbolically) pointing to the actual file. Or you can build a module foo.2.3.so and archive it into libfoo.a. When it's time to update (i.e. provide a new version, mark the old module as load-only (ldedit command), put it into the archive so that existing programs that use that version will still run, and add a new module foo.2.4.so for linking new programs. Repeat as necessary. The convenient thing about archives on AIX is that you can have a single file to house all versions of your modules, not worry about filesystem entries and symlinks (which can create problems) and hides details that the average shouldn't/doesn't care about. |