[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20051003: creating dynamic shared library version of netcdf

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20051003: creating dynamic shared library version of netcdf
  • Date: Mon, 03 Oct 2005 10:54:16 -0600
Unidata Support <address@hidden> writes:

> ------- Forwarded Message
>
>>To: <address@hidden>
>>From: "Sean McBride" <address@hidden>
>>Subject: creating dynamic shared library version of netcdf
>>Organization: Rogue Research
>>Keywords: 200510031547.j93FlgG7016785
>
> Hello,
>
> I am trying to build netcdf 3.6.0p1 as a dynamic shared library, as
> opposed to a static library.  I am using gcc 4.0 on Mac OS X 10.4.
>
> I am not very familiar with automake/configure scripts, but have learned
> enough to build other libraries as shared libs.  In those cases I have
> done this:
>
> ./configure --enable-shared --disable-static
> make
>
> but in the netcdf case, while no error is given for those parameters, I
> still end up with only static libraries.
>
> I'd appreciate any help, or pointers,
>
> Thanks!
>

Sorry, but building a shared library with 3.6.x is going to be
difficult.

We switched to using libtool for netcdf 4.0, which is due out in beta
early next year. That builds shared libraries on the Mac.

There no doubt are settings that will cause the Mac to build a shared
library. But I don't know what they are. Since we have chosen to use
libtool, we don't have to figure that stuff out for each machine,
libtool does it.

Why do you need a shared library?

Thanks,

Ed
-- 
Ed Hartnett  -- address@hidden