Hi,
On Wed, Sep 06, 2000 at 05:28:01PM -0500, Robert Boehne wrote:
>
> Libtool (by it's own admission) will not work for C++
> shared libraries on most platforms.
Yes and no. The multi-language CVS branch addresses the bulk of the
problems.
> Here is a smattering
> of what my OS's/Compilers we currently support without using
> autoconf (i.e. it had better support these at least!)
It does support some of the platforms you listed, but it currently
doesn't support HP aCC because I don't have access to this compiler,
and since no one has contributed a configuration for it. The same
goes for other unsupported platforms/compiler combinations.
[snip]
> I suppose the next reply will be "use the CVS libtool..."
Exactly! :-)
> but I would prefer not to be on the bleeding edge, and
That's understandable.
> in addition to that, I don't want to require users to
> build and install an alpha libtool. (Call me crazy)
Do you mean your end-users or developers? End-users certainly
wouldn't have to build and install libtool. Developers of course
would.
> So is there another answer?
None that I can think of. My own C++ shared library problems prompted
me to contribute to libtool multi-language branch to help stabilize it
as quickly as possible. Hopefully someone else can give you another
option, if libtool isn't suitable for you at this point in time.
-Ossama
--
Ossama Othman <[EMAIL PROTECTED]>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8
