Unix Programming - Mixing shared and static libraries

This is Interesting: Free IT Magazines  
Home > Archive > Unix Programming > January 2007 > Mixing shared and static libraries





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Mixing shared and static libraries
u.int.32.t@gmail.com

2007-01-25, 1:32 am

Hi,

If I compile static libraries that end up in a shared object, when is
this not safe? I understand if the system generates code differently
for the two situations, then it is necessary. Can someone point out to
me which platforms one should do this on?

My *real* requirements are this:

0) Need to unit test
1) Need to unit test same code that is shipped (compiled into a shared
object)
2) Need to use linker script to export the minimal set of public
symbols

The end result *is* a shared object that will be loaded in a plugin
manner. Now if I use a shared object to unit test, I cannot test all of
the code *because* this project also needs to run on Windows (yeah...)
On Windows, for shared objects, all symbols are private unless
exported.

So you can see my dilemma (I hope). What would you suggest?

Thanks!

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com