On Thu, Feb 08, 2007 at 11:39:04PM -0800, Stewart Stremler wrote:
> begin  quoting Jon Wahlmann as of Thu, Feb 08, 2007 at 09:58:28PM -0800:
> [snip]
> > Yup.  SCons is advertised as a "make" replacement along with some
> > autoconf stuff thrown in.  The bonus is it's written using Python,
> > hence the build scripts are Python scripts, which is a much nicer
> > language to program in than "make".
> 
> I never really liked "programming" in Make, even when I was trying
> to get it to do some sorta-kinda sophisticate things.  Ant headed
> in the right direction -- make the build file dumb data, and add
> features to the tool separately.

Yup.  I also like kind of having that ability with SCons.  One can add
functionality to it by adding appropriate Builder or Scanner python
modules.  This way your build script can be as dumb as you want. :-)
Personally, I like a little bit of programmability in my build
scripts, just not the way make does it.

> My Perl is rusty enough to where I need to grab a book to read
> nontrivial Perl code.

I written anything Perl related in years, except for the occasional
CGI script tweak.  For all future scripting projects, it's Python for
me.  It's a case of "I wish I knew then what I know now."  Kind of the
realization that Eric Raymond had when he "finally" first started
working with Python (http://www.linuxjournal.com/article/3882).

> > yet.  Right now it's generating native platform binaries.  Pretty soon
> > I plan on trying to setup up a cross-compiler build environment.  Most
> > likely it'll just be a matter of invoking a different Environment().
> 
> What language are you compiling with it?

It's a simple SNMP management application coded in straight C.  (I
actually roughed it out a bit in a Python prototype.)  The target will
eventually be a deeply embedded board running with just 2M of memory
(no OS).  I'll be using SLIP to talk to a network gateway box that's
to be configured via SNMP.  So, just the minimum to "make it work."

I might need to come up with a script or two to parse out the specific
variables I'm interested in from the vendor's MIBs to generate
pre-encoded versions of the OIDs.

-Jon


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to