wn projects. The attached example already detects a hell
of a lot different libs, header files, etc.
All you need to edit is configure.in. I think everything will speak for
itself.
THERE ARE ABSOLUTELY NO DEPENDENCIES EXCEPT SOME WORKING C COMPILER.
(It is prepared for Windows sup
Guido Draheim wrote:
> https://sourceforge.net/forum/forum.php?forum_id=665363
>> As of 2007-02-08, SourceForge.net Compile Farm service
>> has been officially discontinued.
>
>> We feel that our resources are best used at this time
>> in improving other parts of our existing SourceForge.net
>> se
Guido Draheim wrote:
> Dirk schrieb:
>> Guido Draheim wrote:
>>> https://sourceforge.net/forum/forum.php?forum_id=665363
>>>> As of 2007-02-08, SourceForge.net Compile Farm service
>>>> has been officially discontinued.
>>>> We feel that our
aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.
./autogen.sh: line 47: intltoolize: command not found
There... bullshit spewing autoconf again... can someone explain to me
what's so "auto" abou
My point is that autoconf is such a bloated, self-important,
wet-script-kiddie-dream that is DOESN'T make the build process easier...
It rather encourages people to write their own config scripts...
So the whole thing has lost its meaning...
Stewart Dean wrote:
I am continually astounded by self-righteousness in the tech world.
There is so much all of us either don't know (to say nothing of what we
don't know that we don't know) or have bunged up in our time, that we
should be um temperate in what we say. We all have plen
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
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
when i probe for byteswap.h in config.log appears
#define HAVE_BYTESWAP_H
that is great!
but how do i include this precious information into the compile
process.. dont tell me #include "config.log" or i'll unsubscribe at once!!!
Thanks,
Dirk
how can i make autoconf probe for a parallel port?
Thanks,
Dirk
how would i find out if ipv6 is available (enabled)?
hit suck. It will take some time until I can give "constructive
critiques" about autoconf again.
Thanks,
Dirk
12 matches
Mail list logo