On Sat, Sep 4, 2010 at 00:02, Christopher Sean Morrison <[email protected]> wrote:
>
> On Sep 3, 2010, at 5:55 PM, Tom Browder wrote:
>
>> Attached is an m4 source file to be input to m4 to generate a special
>> header file in the include directory to satisfy my itch to have some
>> cpp-usable macros for conditional compilation.  Note that it doesn't
>> have to be used by anyone, but it does do the job if anyone wants to
>> use it.
>
> Thanks for sharing those, Tom.  I don't consider the version
> management a settled issue in the least so it's good to simply be
> reminded along with details and progress.

Kind words--thanks.

>> Note that the m4 file is fragile unless you really know what you are
>> doing (and it was hit and miss for me even with help from the boys on
>> the m4 mailing list--everyone has a different idea).
>
> Fragile in what sense?

Well, in the sense that fiddling with the file can inadvertently add
unwanted spaces or stop macros from working--not as familiar to many
of us compared to other languages--my own shortcoming anyway.

>> I have tried to get it into the build system but haven't succeeded
>> yet; however, I have a simple Makefile attached for testing.
>
> Make sure you're not fighting the cache.  Adding new m4 macro files
> requires rebuilding via aclocal along with sometimes needing to wipe
> out the autom4te.cache.  The autogen.sh script will do some of this
> for you, but it can still be a hassle every once in a while.  A fresh
> checkout with the mods added before attempting to build

I don't know how all that plays together.  I see this m4 invocation as
not truly part of the autoconf suite--it doesn't rely on anything
outside the one m4 file and m4 built-ins.  I would have done the thing
in Perl but know that we want to rely on more "portable" build tools
if at all possible.  (Before I pass i would love to have the
POSIX/FSF/GNU folks declare that Perl is as portable as bash and
expected to be in any modern non-embedded POSIX computer system.)

I'll keep looking at integrating it for seamless build and
installation automation and, though.

Cheers,

-Tom

Thomas M. Browder, Jr.
Niceville, Florida
USA

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to