Very Computer

--
Fletcher Glenn
to reply remove NOSPAM from my reply address

| I am trying to build a dynamic library to replace both a static library
| which supports legacy code, and a collection of the same routines which
| has been recompiled with _REENTRANT defined to support some new code.
| My problem is that the legacy code would need to use the non-reentrant
| version of the routines, and the new code needs the reentrant versions.
| How can I include both versions in the library, and assure that the
| correct version is used in each case?

Why does the legacy code need the non-reentrant version?  Have the
API or functional semantics changed?  Ordinarily, reentrant code
should work in cases where non-reentrant would, unless the caller
has become dependent on non-reentrant effects.

Basically, you'll need to make 2 different libraries.  Just set up
two Makefiles, one to build the reentrant library, and one to build
the non-reenentrant library.  If you can do it with common source,
that's fine.  Define a symbol for the C code to test if the code
needs to be different.  Be sure you don't get .o files mixed up.
One way to do that is to do actual builds into separate copied
directory trees from the pristine (uncompiled and clean) sources.

When compiling the application code, then just link them to the
appropriate library by the variant names.

--
| Phil Howard - KA9WGN | My current websites: linuxhomepage.com, ham.org
| phil  (at)  ipal.net +----------------------------------------------------