Hello Robert and Jelmer, and thanks for your replies.
On Tuesday 22 March 2011, Jelmer Vernooij wrote:
> On Tue, 2011-03-22 at 10:48 +1300, Robert Collins wrote:
> > On Tue, Mar 22, 2011 at 8:41 AM, Stefano Lattarini
> > > to its suboptimal documentation. So I'm going to ask: Robert, as
> > > the
On Mon, Mar 21, 2011 at 3:09 PM, Nick Bowler wrote:
> * Modify gnulib so that it can be easily integrated into a
> non-recursive automake setup. One could look to libltdl for
> inspiration here.
How about modifying GCC. That should take some time, I think :) :) :)
On 2011-03-22 07:36 -0700, Ben Pfaff wrote:
> Nick Bowler writes:
>
> > * Modify gnulib so that it can be easily integrated into a
> > non-recursive automake setup. One could look to libltdl for
> > inspiration here.
>
> It doesn't have to be modified. An Automake setup can easily an
Nick Bowler writes:
> * Modify gnulib so that it can be easily integrated into a
> non-recursive automake setup. One could look to libltdl for
> inspiration here.
It doesn't have to be modified. An Automake setup can easily and
usefully contain a mix of recursive and non-recursive
su
On Tuesday, March 22, 2011 01:54:33 am Paul Elliott wrote:
> I have a c library that currently uses an old style Makefile that I want to
> convert to auto*tools.
>
> One .c file is used as a .h file. That is, it is included by another .c
> file and it should not be itself compiled. Why the author
On 03/22/2011 07:54 AM, Paul Elliott wrote:
I have a c library that currently uses an old style Makefile that I want to
convert to auto*tools.
One .c file is used as a .h file. That is, it is included by another .c file and
it should not be itself compiled. Why the author did this I do not know
Paul Elliott writes:
> I have a c library that currently uses an old style Makefile that I want
> to convert to auto*tools.
> One .c file is used as a .h file. That is, it is included by another .c
> file and it should not be itself compiled. Why the author did this I do
> not know, but I do not
