@corto
Quote:
1. What are the difference between -rpath et -rpath-link ? What do they do exactly ?
http://en.wikipedia.org/wiki/Rpath_%28linking%29Quote:
2. Is it planned to add the version tag in shared objects provided in the system ? It would be easier for updates and version control.
yes. is planned
Quote:
3. Should we check the availability of shared objects in SOBJS: at the beginning of our programs ? Does it crash if the shared object is missing ? I did not tried yet.
The new elf.library will tell you if a (and which) shared object is missing and will print a "file is not executable" when you click on ok
Quote:
4. To avoid links in the SDK lib directory, would it be possible for the compiler to check the path SOBJS: first ? In the article, it is told that "-lSOBJS:" can be added in order to find shared objects in SOBJS:, is it really the case ? It does not seem to work here.
IIRC it will first check the PROGDIR: and then SOBJS: (or the countrary). Snoopy will tell you
I prefer to put my .so in SOBJS: because actually there are a lot of differents .so files. we need a good repository
Quote:
5. For the provided shared objects, could you also put the includes in the SDK ? I think about freetype, I am confused with 2 old libs from os4depot and a shared object without includes (maybe I overwrote them ...).
The include files are same of the staic version one
Quote:
6. Could someone document more about shared objects, options (like syntax about -rpath, etc.) ?
I think google will help you alot.. :D
Quote:
7. I wonder how versions will be managed because we have already started to create links concerning libSDL / libSDL-1.2, libpng / libpng12, ...
Usually .so files came with a version number, so you can have multiple version libraries and usually the one without number is a link to the last version.