On one of my machine, a full build tree that otherwise works well, gives
me the following weird problem:
shared libraries are installed without the .so extension ?!??!
Has anybody encountered this before? It used to work on this machine, I
changed some stuff (that I cannot backtrace) and now it
Alexandre Duret-Lutz wrote:
"sashan" == sashan <[EMAIL PROTECTED]> writes:
sashan> Hi
sashan> How do I execute a copy (cp) of some files once they are generated by
sashan> automake. The situation is I have a automake/autoconf/libtool
sashan> generated library that is loadable by python. l
Hi,
Two questions. I am building a package with a convenient library that is
then used by some other library/program that the package install. The
base library is libbase and the Makefile.am for it looks like this:
lib_LTLIBRARIES = libbase.la
libbase.la_SOURCES = base.C
A subsequent library is
Hi,
I am writing a install-exec-hook and the appropriate uninstall-hook. The
former simply makes a copy of installed lib somewhere else, and the
later needs to delete it. For that I simply wrote:
uninstall-hook:
rm -f foo.so
What is the correct variable to ask for removal of a file. Is this $
Hi,
I am compiling a project with a swig generated file. Swig is a tool that
takes a foo.i file and generates a foo_wrap.cxx (it can do more but no
our concerne here ;-)).
In my Makefile.am, I put:
line 1: foo_wrap.cxx: foo.i
line 2: $SWIG -c++ -python foo.i
line 3:
line 4: BUILT_SOURCES:
