build order with shared libs

[Andreas Pakulat]

Hi,

I just re-introduced shared libs in kdevelop4's python plugin (living in
playground/devtools/kdevelop4-extra-plugins/python) and found that the
shared lib for the parser would be built _after_ the one for the duchain
even though the duchain-lib links to the parser lib and uses headers
from the parser lib.

Any idea whats happening there? (This of course only happens on a make
clean and I don't have the parser lib installed)

On a side note: could it be that creating shared libraries without
soname (as we're doing for some of our internal stuff in kdevelop4) sets
the visibility to default instead of hidden? Because the export macro's
for those libs in kdevelop4 were broken (i.e. the classes were not
exported) but everything still linked (in a clean build). And similar
the aforementioned duchain lib didn't have export macro's at first but
the plugin could properly link to it nonetheless. Is that expected?

Andreas

-- 
Don't worry so loud, your roommate can't think.