Re: Macro to select c++ as default compiler for c files.

On 3 November 2014 11:28, Lakshmi M wrote: > Hi All, > > I am working with autotools and i wish to use c++ compiler by default for > compiling my c files. > > USUAL behaviour : > ex : myexecutable_SOURCES = file.cpp -> uses c++ compiler > myexecutable_SOURCES = file.c -> uses

Re: Automake 1.14 and subdir-objects

On 14 August 2014 00:56, David Beer wrote: > Gavin, > > I am going to test out and see if the BUILT_SOURCES option works. Making a > single Makefile would not be an option as there are over 500 Makefiles in > my project and combining them into one would not be maintainable. > I am not sure if lo

Re: only installing shared versions of some libs

On 10 December 2013 09:47, Daniel Pocock wrote: > > > I've recently adapted a project to support DSO plugins/modules > > The existing project includes normal libraries and binaries. In a > normal build, we want to > > a) build and install the shared and static versions of the normal libraries > >

trivial typo fix

Hi. I am attaching a trivial typo fix patch. -- VZ missing.diff Description: application/itunes-itlp signature.asc Description: OpenPGP digital signature

Re: managing headers in source

On 07/20/2013 12:52 PM, Simon Richter wrote: > Hi Václav, > >> - src/Makefile.am: Listing headers for dependencies and source >> files. >> (http://bazaar.launchpad.net/~log4cplus/log4cplus/trunk/view/head:/src/Makefile.am) > >> > You do not need to list the headers as source files as long as the

managing headers in source

Hi. I am using Automake in log4cplus project and I wonder if it is possible to improve the organization of Makefile.am files so that when I add a header file, I do not have to modify both of these files: - include/Makefile.am: Listing headers so that they get installed properly. (http://bazaar.la

Re: looking for a good example of non-recursive Make using project

On 11/17/2012 11:36 AM, Vincent Torri wrote: > On Sat, Nov 17, 2012 at 11:13 AM, Václav Zeman wrote: >> Hi. >> >> I am looking for a good example of a project with non-recursive Make >> that is using Automake, that is not trivial. I would like to convert my >> pro

looking for a good example of non-recursive Make using project

Hi. I am looking for a good example of a project with non-recursive Make that is using Automake, that is not trivial. I would like to convert my project, log4cplus, to non-recursive Make style, if it is possible. Any recommendations? -- VZ signature.asc Description: OpenPGP digital signature

building without $(top_builddir) in LDADD (was Re: libtool libraries, dependencies and parallel builds)

On 11/02/2012 09:43 AM, Stefano Lattarini wrote: > On 11/02/2012 09:18 AM, Václav Zeman wrote: >> On 1 November 2012 17:42, Diego Elio Pettenò wrote: >>> On 01/11/2012 09:18, Vincent Torri wrote: >>>> lib_eo_libeo_la_LIBADD = $(top_builddir)/src/lib/eina/libeina.la &g

Re: libtool libraries, dependencies and parallel builds

On 1 November 2012 17:42, Diego Elio Pettenò wrote: > On 01/11/2012 09:18, Vincent Torri wrote: >> lib_eo_libeo_la_LIBADD = $(top_builddir)/src/lib/eina/libeina.la > > Don't use $(top_builddir) and it should work just fine. Is there a rationale behind this? I am not saying it is wrong, I just want

Re: problem with AM_PATH_PYTHON

On 10/26/2012 07:30 PM, Stefano Lattarini wrote: > [Re-adding Václav in CC, please don't drop it in the future] > > On 10/26/2012 06:47 PM, Robert Boehne wrote: >> On 10/26/12 09:04, Stefano Lattarini wrote: >> >> [SNIP] >> >>> This doesn't look like output from the Automake-provided AM_PATH_PYTHON

problem with AM_PATH_PYTHON

Hi. I am having a problem with AM_PATH_PYTHON. I have this in my configure.ac: AS_IF([test "x$with_python" = "xyes"], [AM_PATH_PYTHON([2.3], [:], [:]) AX_SWIG_PYTHON AC_CONFIG_FILES([swig/python/Makefile])]) The problem is that when I am cross compiling it ignores the if-block and puts