I try to mount my project on Autoconf.
it has very heterogeneous software parts, e.g.
(1) fat POSIX host (typically HOST=BUILD=`config.guess')
(2) ARM-based microcontroller without external memory
(I am used to build tools with arm-elf- prefix)
(3) little AVR appendices.
(2) and (3) are written
On Mon, Mar 17, 2008 at 9:28 PM, epswint <[EMAIL PROTECTED]> wrote:
> -Can autoconf/automake determine the code dependencies (e.g. follow the
> #include trail) and put those in the Makefile?
If your configure script detects GCC, then yes, your build system will
automatically follow the #include
On Mon, Mar 17, 2008 at 7:35 PM, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 17, 2008 at 05:53:48PM +0200, Bernd Jendrissek wrote:
> > Ideally that would be just "autoreconf -i" in all autoconfiscated projects.
>
> well, why "-i". Shouldn't it _ideally_ be just "autoreconf"?
Touche
On Tue, Mar 18, 2008 at 9:48 AM, Ineiev <[EMAIL PROTECTED]> wrote:
> I try to mount my project on Autoconf.
> it has very heterogeneous software parts, e.g.
>
> (1) fat POSIX host (typically HOST=BUILD=`config.guess')
> (2) ARM-based microcontroller without external memory
> (I am used to buil
Paul Smith wrote:
On Mon, 2008-03-17 at 15:37 +0100, Dirk wrote:
I HAVE written something that works better than autoconf... in the
real world... that requires only a installed C compiler... and is so
easy it makes autoconf look like a project whose purpose is to harm
open source development...
--- Bernd Jendrissek <[EMAIL PROTECTED]> wrote:
[snip]
> With some
> shell / batch file magic I was able to get "./configure
> --host=unknown" to generate a config.h for the DOS / TopSpeed C
> environment, that I then renamed and kept as a precious artifact.
> After another "./configure --host=`c
Hi,
On Tue, Mar 18, 2008 at 10:35:55AM +0200, Bernd Jendrissek wrote:
> It's just that my sense of aesthetics is offended by the existence of
> a *thousand* such collections of a "few lines" of shell in a
> customised ./{autogen,bootstrap}.sh amongst all the autoconfiscated
> packages out there.
John Calcote wrote:
Dirk,
I once thought as you did (albeit without quite so much volatility).
I've since come to realize that autoconf and the rest of the autotools
are really quite amazing.
The problem most people have with the autotools is that they exist at
the 10,000 foot level (metaphoric
On Tue, Mar 18, 2008 at 9:05 AM, Dirk <[EMAIL PROTECTED]> wrote:
> I know pretty well what I'm talking about. I was using autoconf for some
> months to configure my projects but then switched to my own solution
> because autoconf was just bloated overkill... overkill that forced me to
> spend t
Dirk.
You have made your point now would you please stop polluting this mailing list
with your unhelpful and unproductive postings. I'm sure you have better things
to do with your time than try and stir up trouble in the Autotools community.
___
Auto
Since your last post seemed to be a bit more willing to engage in a
dialog, I'll send this then I'm done. Some of these points have been
made already but maybe some concrete examples will help.
You have two misconceptions which are contributing to your frustration,
I think: the first and largest
Hi Paul,
I do hate contributing to this thread, but way back at the beginning,
I believe I remember that his irritation began with with some indecipherable
"command not found" message. I found the same thing quite frustrating.
I also complained (somewhat more politely :), and now Ralph has augmen
Hi,
I've seen people reporting `configure' failures due to
"cannot compile sizeof (char)". Investigating the issue, it turned out
to be that, in a native compilation environment, the executable produced
by `AC_COMPUTE_INT' could not be run because some library specified in
`$LIBS' was not in `$LD
Hello Ludovic,
* Ludovic Courtès wrote on Tue, Mar 18, 2008 at 09:36:58PM CET:
>
> I've seen people reporting `configure' failures due to
> "cannot compile sizeof (char)". Investigating the issue, it turned out
> to be that, in a native compilation environment, the executable produced
> by `AC_C
Hi,
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> But a library that will not be found by the runtime linker is a problem
> for all run tests, not just AC_COMPUTE_INT. The normal way to go about
> this is to ensure that libraries are found; see for example the macros
> from the gnulib module 'ha
On Tuesday 18 March 2008 02:28, John W. Eaton wrote:
> On 17-Mar-2008, Keith Marshall wrote:
> | I've recently ported Andries Brouwer's, (now Federico Lucifredi's),
> | variant of John Eaton's man program, for use with MSYS, under
> | MS-Windows. That package came with a hand crafted configure
> |
* Ludovic Courtès wrote on Tue, Mar 18, 2008 at 11:27:11PM CET:
>
> My understanding is that, provided we use, e.g., `AC_LIB_LINKFLAGS' to
> search for a lib instead of `AC_CHECK_LIB', the link flags will
> contain appropriate `RPATH'-related options, such that the resulting
> executables will jus
It is not useless, configure works quite well, when it doesn't it is a pain tho.
For the developer, no matter how you put it, it takes a huge effort to create
and
Maintain a configure script, and its so ugly.
IMO, I'd love to see it evolve to something advanced like using a customised
Small lan
Paul Smith wrote:
Since your last post seemed to be a bit more willing to engage in a
dialog, I'll send this then I'm done. Some of these points have been
made already but maybe some concrete examples will help.
I've heard various complaints about autoconf and automake over the years
and he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Smith on 3/18/2008 12:53 PM:
| Since your last post seemed to be a bit more willing to engage in a
| dialog, I'll send this then I'm done.
| You have two misconceptions which are contributing to your frustration,
| I think: the firs
Bruce Korb wrote:
> I do hate contributing to this thread, but way back at the beginning,
> I believe I remember that his irritation began with with some indecipherable
> "command not found" message.
I hate adding to it as well. But just to keep the records straight
the original complaint was abo
21 matches
Mail list logo