Hello Maxim,
I recommend you to read the tutorial at
http://www.lrde.epita.fr/~adl/autotools.html . It addresses all of your
questions. See below:
> i am triing to produce such functionality:
> 1) source file from one subdirectory can include source file from another
> directory. For example,
On Sun, Sep 27, 2009 at 9:43 AM wrote:
> * Steffen Dettmer wrote on Wed, Sep 23, 2009 at 11:26:33AM CEST:
> > On Tue, Sep 22, 2009 at 10:35 PM, wrote:
> > > Not AFAIK. It works because automake adds -I. by default.
> >
> > Yes, unfortunately it adds it.
>
> You can avoid that with the 'nostdinc'
On Sun, Sep 27, 2009 at 11:45 PM wrote:
> Good Day, dear GNU community :-)
>
>---
> .
> |-- Makefile.am
> |-- base
> | |-- Makefile.am
> | |-- err
> | | |-- err.cpp
> | | `-- err.h
> | |-- io_base.cpp
> | |-- io_base.h
> |-- graph
There is an article called "recursive make considered harmful".
According to it, you should have just one Makefile.am in top level
with all the rules (all libs etc). By this, make can show its
strengths best. Often, a Makefile.am "per directory" seems to be
used, but for a new projec
> There is an article called "recursive make considered harmful".
> According to it, you should have just one Makefile.am in top
> level with all the rules (all libs etc). By this, make can show
> its strengths best. Often, a Makefile.am "per directory" seems
> to be used,
On Mon, 28 Sep 2009, Alfred M. Szmidt wrote:
There is an article called "recursive make considered harmful".
According to it, you should have just one Makefile.am in top level
with all the rules (all libs etc). By this, make can show its
strengths best. Often, a Makefile.am "per director
On Sep 28, 2009, at 12:04, "Alfred M. Szmidt" wrote:
There is an article called "recursive make considered harmful".
According to it, you should have just one Makefile.am in top level
with all the rules (all libs etc). By this, make can show its
strengths best. Often, a Makefile.am "per
On 09/28/2009 05:55 PM, Bob Friesenhahn wrote:
On Mon, 28 Sep 2009, Alfred M. Szmidt wrote:
There is an article called "recursive make considered harmful".
IMO, one of the most overrated articles of all times.
According to it, you should have just one Makefile.am in top level
with all the ru
On Mon, 28 Sep 2009, Ralf Corsepius wrote:
The main advantage of a Makefile per directory is that it makes it
easier to request building seperate parts of the tree.
Right. Exactly this is a huge win in bigger projects.
Not necessarily. Even with some smaller projects (e.g. libtiff) I
usuall
Hello,
Under weaknesses for `dirname' the manual (v2.64) mentions that one
should use macro AS_DIRNAME instead. The macro seems to do what I want,
but I cannot find it in the manual? Is it safe to use that macro or
should I consider it as an internal..?
Thanks,
Peter
--
Peter Johansson
svn
10 matches
Mail list logo
