Re: adding conditionally a c++ file implies static linking with g++

[Ralf Wildenhues]

[ let's drop the automake list ]

* Vincent Torri wrote on Sat, Nov 20, 2010 at 12:55:27AM CET:
> 
> Now, i've remarked a side effect. What I'm building is a shared lib
> that is only opened by dlopen. So I pass --tag=disable-static to
> pdf_la_LIBTOOLFLAGS. When using foo_LINK, the static lib is build,
> hence installed. Is there a way to forbid the build of the static
> lib.
> 
> Of course, I can always delete it during install with the
> install-data-hook rule, but i would like to not build it.

Please show a small full example, that way it is easier to see what code
exactly you have, and what is happening.

If you need a small example setup to start with:

cat >configure.ac <<\EOF
AC_INIT([a], [1])
AM_INIT_AUTOMAKE([foreign])
AC_PROG_CC
AC_PROG_CXX
AC_PROG_LIBTOOL
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
EOF

cat >Makefile.am <<\EOF
lib_LTLIBRARIES =
EOF

autoreconf -vi

Cheers,
Ralf