Re: building a shared library that depends on a static library

Hi Jason, * Jason Kraftcheck wrote on Fri, Mar 03, 2006 at 05:45:23PM CET: Is there some way I can force configure to change the deplibs_check_method? By integrating libtool.m4 into your package and changing it (more details if you're interested). With recent Automake, this isn't

Re: prevent building static library

Hi Tommi, * Tommi Mäkitalo wrote on Thu, Mar 02, 2006 at 08:35:48PM CET: when building libraries with LTLIBRARIES automake build static and dynamic versions of them. But I would like to build only the dynamic one. How can I tell automake not to build static libraries? This article, and

Re: Adding BUILT_SOURCES to a multi-directory, non-recursive project

DG == Duncan Gibson [EMAIL PROTECTED] writes: [...] DG # autotools object to --libs, FLTK_LIBRARIES FLTK_LDFLAGS :-( DG # FLTK_CXXFLAGS = `fltk-config --cxxflags` DG # FLTK_LIBRARYS = `fltk-config --libs` DG # FLTK_LDSFLAGS = `fltk-config --ldstaticflags` You could AC_SUBST these

Re: problem with flex scanner `make dist'

tf == tom fogal [EMAIL PROTECTED] writes: tf Been a while since I've followed any autotools list; sorry if I've tf missed the answer to this issue... tf I have a project with a flex scanner that must be compiled with a C++ tf compiler (just for linking purposes; I'm not using the C++ flex

problem with flex scanner `make dist'

Been a while since I've followed any autotools list; sorry if I've missed the answer to this issue... I have a project with a flex scanner that must be compiled with a C++ compiler (just for linking purposes; I'm not using the C++ flex interface). It seems the way to do this is to name it

Re: building a shared library that depends on a static library

* Ralf Wildenhues wrote on Fri, Mar 03, 2006 at 06:10:21PM CET: cheap workaround of the day: disable shared libs on problematic platforms: put this in configure.ac before AC_PROG_LIBTOOL: AC_ENABLE_SHARED case $host in hppa*|x86_64*|s390* | *-solaris*|*-sunos*) AC_DISABLE_SHARED ;;

Re: building a shared library that depends on a static library

Hi Jason, * Jason Kraftcheck wrote on Tue, Feb 28, 2006 at 02:42:34AM CET: Automake includes the contents of the $LIBS variable in all link commands, including linking libraries. This results in the following behavior: 3) If libtool is creating a shared library, and one or more of the

building a shared library that depends on a static library

Automake includes the contents of the $LIBS variable in all link commands, including linking libraries. This results in the following behavior: 1) If libtool is creating a static library, this seems to work fine. The libraries in $LIBS are listed as dependencies in the resulting .la file. 2)

How to use BUILT_SOURCES in non-recursive, multi-directory project?

I've been trying to set up a multi-directory project using non-recursive auto{conf,make} to build an FLTK application (see http://www.fltk.org). I have created a simple example for testing, where I have a sub-directory containing foo.fl and foo_test.cxx, and what I need to do is: use 'fluid

best aclocal include practice wanted

Hi, what is the recommended way to include project-written m4 macros ? I include the macros in project-root/config/m4 and call in autogen.sh aclocal -I config/m4 The config directory itself is configured in configure.ac with AC_CONFIG_AUX_DIR(config). Is there something wrong with this

Re: Copying a file after each subdirectory build

RS == Russell Shaw [EMAIL PROTECTED] writes: RS Hi, RS I have lots of libraries and programs in separate directories, each RS with its own configure.ac and Makefile.am. RS What can i put into Makefile.am so that after each library is built, RS it will copy its header file and object file

Re: building a shared library that depends on a static library

Ralf Wildenhues wrote: Hi Jason, * Jason Kraftcheck wrote on Tue, Feb 28, 2006 at 02:42:34AM CET: Automake includes the contents of the $LIBS variable in all link commands, including linking libraries. This results in the following behavior: 3) If libtool is creating a shared library,

Re: best aclocal include practice wanted

Thomas Porschberg [EMAIL PROTECTED] writes: what is the recommended way to include project-written m4 macros ? Many projects use a directory named m4, but there is no common convention. I include the macros in project-root/config/m4 and call in autogen.sh aclocal -I config/m4 The config