Re: creating C++ libs contitionally

2005-03-14 Thread Mattias Barthel
Hello. Now I tried to just have as baselib_LTLIBRARIES. But it sure does not create any DLL. AUTOMAKE_OPTIONS = foreign corename = libbkio basename = $(corename) ##INCLUDES = -I../include -I$(MACROPKG_INCLUDEDIR) -I$(PYTHON_INCLUDEDIR) ##CXXFLAGS = @CXXFLAGS@ -DSWIG_GLOBAL

Re: creating C++ libs contitionally

2005-03-12 Thread Ralf Wildenhues
Hi Matthias, Please Cc: the automake list on replies, so others can help as well. * Mattias Barthel wrote on Tue, Mar 01, 2005 at 10:56:50AM CET: > Ralf Wildenhues wrote: > >* Mattias Barthel wrote on Wed, Feb 16, 2005 at 06:50:10PM CET: > > > >>I am passing my Makefile.am's from 1.4 to 1.6. > >

Re: creating C++ libs contitionally

2005-03-01 Thread Ralf Wildenhues
Hi Mattias, * Mattias Barthel wrote on Wed, Feb 16, 2005 at 06:50:10PM CET: > > I am passing my Makefile.am's from 1.4 to 1.6. You should try to use a *recent* Automake. Like 1.9.x. > Doing this I have encountered numerous incompatibility problems. Oh well. > First when starting with 1.4, a

creating C++ libs contitionally

2005-02-16 Thread Mattias Barthel
Hello. I am passing my Makefile.am's from 1.4 to 1.6. Doing this I have encountered numerous incompatibility problems. First when starting with 1.4, a part of the problem I bumped in to was that libtool did not really understand .dll as an extension of a lib, me having to make the Makefiles compat