I produced hereafter some information about shared libraries on different systems. However, this information is probably very sparse on details and may even not be up-to-date. Actually, keeping track of changes is nearly impossible. The definitive information usually comes from the operating system docs. (e.g. HP's "HP-UX Linker and Libraries User's Guide", Sun's "Linker and Libraries Guide", SGI's "MIPSpro Compiling and Performance Tuning Guide", IBM's "AIX Linking and Loading Mechanisms", etc.), where there is often advice on the best options for performance. Using static and shared libraries across platforms Using static and shared libraries across platforms
I often work with teams getting started with Eclipse RCP, and the most common complaint I hear is that it’s too hard to set up automated builds. PDE Build can be frustrating to work with because it’s a black box. Your code goes in one side and a fully branded RCP application pops out the other. But if something goes wrong inside the box, where do you start to debug? In my opinion, the best way to work with PDE Build is to get a very simple build running in your environment. Getting started with PDE Build « RCP Quickstart: Eclipse Rich Client Platform Tips, Training and Consulting Getting started with PDE Build « RCP Quickstart: Eclipse Rich Client Platform Tips, Training and Consulting
6 Great Links for Eclipse Build Automation with PDE Build