> even after spending a few hours wading through info(1) pages, I'm
> still not getting it.
My observations about GNU Autotools
(1) WHat's the problem? Is it getting the "correct" version of
autoconf
to run? If so the best "fix" is to put a line in configure.ac
that reads "AC_PREREQ(X.YY)" with X.YY being a the LOWEST number that
could possibly work. You do not want to force everyone to use a
newer version of autotools unless that new autotools has a
"life or death, must have" feature.
(2) End users, (those are the people who compile and run but don't
do development) should not have to have autotools installed. They
will run the configure script. Developers for the most part
will use "autoreconf", user will run ./configure
(3) Never, never, write code that reads like #ifdef SOLARIS or
#ifdef BSD. This a absolutly wrong and may break with the
next release of the OS. Always test for required features
99% of the time the "autoscan" tool will build a "good enough"
configure.ac file for you. Add some minor stuff to check for
libraries, drivers and such and you're done. If configure.ac
looks complex something is either wrong or you need to re-organize
the source code into smaler directories
>
Chris Albertson
Home: 310-376-1029 [EMAIL PROTECTED]
Cell: 310-990-7550
Office: 310-336-5189 [EMAIL PROTECTED]
KG6OMK
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
_______________________________________________
Openpbx-dev mailing list
Openpbx-dev@openpbx.org
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
