Re: [paragui-users] os target base?

[Asko Kauppi]

(disclaimer: i've never really dug into auto* for real, so may be 
misinformed)

Imho, auto* is not fully scriptable. By "fully scriptable" i mean a 
general-purpose scripting language (s.a. Python, Perl, Ruby, Lua..) 
that is controlling the thing, not a 'scriptable' make engine (s.a. 
make, auto*?, jam..)

Benefits? You can transparently merge _any_ kinds of analysis & 
decision making with the build script. Really a Good Thing(tm) ;).

Any users of SCons (or its godfather Cons) in this neighborhood?

p.s. Dependency of cygwin for Windows builds is a shortcoming, imho.

-ak


Teunis Peters kirjoittaa perjantaina, 25. heinäkuuta 2003, kello 03:04:

> On Fri, 25 Jul 2003, Asko Kauppi wrote:
>
> > What's the current/intended OS target base for ParaGui?
>
> from what I know it was originally designed for linux/fb - in embedded
> application.  (a fax machine IIRC :)
>
> > The reason i'm asking is, i don't really like auto* (and many people
> > might share).
> >
> > In addition, i've created a fully scriptable building environment that
> > beats the hell out of auto* in many ways. Simplicity being one of 
> > them.
> >
> >
> > Are you interested? Should we try switching?
>
> auto* -is- a fully scriptable building environment.
> The trick is dependancies.  auto* requires perl.  Could be done with
> python, perl, ruby, whatever.
>
> I don't know what the rest of y'all think but I'm happy enough with 
> auto*.
> At least I can build binaries for multiple platforms from the same
> directory tree (i686-linux, i686-cygwin could be done as subdirs for
> build).  I only use one at the moment...
>
> G'day, eh? :)
>         - Teunis
>
>
>
> _______________________________________________
> paragui-users mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/paragui-users