Re: [Ngspice-devel] ngspice as shared lib [v2]

[Ernesto P. <ep...@gm...>]

To anyone automating the builds I'd advise to clean up between consecutive
compilations. I remember when I first tried to compile it on Linux I did a
make install, then realised I needed the corresponding option for the
shared library, so I ./configured etc again; the resulting library wouldn't
work, complaining about an undefined symbol. The solution was to make clean
and repeat. I haven't tried again with version 27 but it might still be the
case.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On 29 September 2017 at 22:06, Holger Vogt <hol...@un...> wrote:

> The difference between the two *.cm is that when compiling shared ngspice
> library, the gcc compiler flag -fvisibility=hidden is used to hide all but
> the exported symbols. This is inherited from compiling the ngspice lib
> itself.
>
> The stored symbol table is smaller, thus the library size is smaller.
> Still both are working the same.
>
> This flag is not used when compiling standard ngspice. For the small *.cm
> with only few symbols this is not a serious problem.
>
> Holger
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Ngspice-devel mailing list
> Ngs...@li...
> https://lists.sourceforge.net/lists/listinfo/ngspice-devel
>