Title: Hello The reason for this email is to introduce myself and to see
if there is anything we could do to help each other out
Hello
fellow internet marketer.
#recipient#
>> What I ended up doing is building the swig/python modules with
>> automake.
...
>> The missing link I had to fix with automake/python module support was
>> that python wouldn't load uninstalled automake shared objects as
>> python extensions. The solution was to writ
I've been struggling with this, and cannot seem to find any examples of
other people doing the same... but I'd like to be able to have
automake/configure create makefiles that put the .o, .a, executables,
etc in another directory based on a configuration parameter.
I did this by hand-editting
So what options exist for making a single top-level monolithic Makefile.am?
I can't imagine keeping this file up-to-date by hand, especially on a large
project where changes must be frequently made by multiple developers.
Ideas?
H
Run the configure script twice.
Once from $(srcdir)/build/Release with CFLAGS=-O3 CXXFLAGS=-O3
Once from $(srcdir)/build/Debug with CFLAGS="-O -g" CXXFLAGS="-O -g"
Cheers,
Rob
On Thu, 2002-05-02 at 23:19, Harlan Stenn wrote:
> So what options exist for making a single top-level monolithic Makefile.am?
>
> I can't imagine keeping this file up-to-date by hand, especially on a large
> project where changes must be frequently made by multiple developers.
>
> Ideas?
I spl
Harlan Stenn wrote:
>
> So what options exist for making a single top-level monolithic Makefile.am?
>
> I can't imagine keeping this file up-to-date by hand, especially on a large
> project where changes must be frequently made by multiple developers.
>
> Ideas?
Autogen based on definitions in
Does anybody have some examples of how this works?
And is it possible to go to any spot in the tree and have a "make" do a
monolithic (non-recursive "make") build of the descendent hierarchy?
H
I've implemented that myself, but only using autoconf,
not automake. I'd be happy to post a description if
it's of interest. The basic idea is to make sure
all variables are fully qualified so there are no clashes
between any Makefile fragments in the whole system.
(I also prefer to avoid phony
