bjam and tcl

Does anyone have experiences to share regarding the use of bjam for
complicated tcl projects? I'm rethinking our build process and pondering
make vs all of the make alternatives. Jam (or Boost.jam) seems to be the
healthiest alternative to make; however, it looks like one would need to
script up some jam code to handle tcl builds. I was wondering if someone
has already created jam files for tcl projects.

--
sheila

sheila miguez wrote:
>
> Does anyone have experiences to share regarding the use of bjam for
> complicated tcl projects? I'm rethinking our build process and pondering
> make vs all of the make alternatives. Jam (or Boost.jam) seems to be the
> healthiest alternative to make; however, it looks like one would need to
> script up some jam code to handle tcl builds. I was wondering if someone
> has already created jam files for tcl projects.
>
> --
> sheila

You have also considered bras? (I do not know anything about bjam, nor
your particular Tcl projects, but bras seems quite capable of handling
complicated builds ...)

Information on bras: http://wiki.tcl.tk/5975
Regards,

Arjen

On Thu, 23 Dec 2004 09:39:39 +0100, Arjen Markus wrote:
> sheila miguez wrote: 

> You have also considered bras? (I do not know anything about bjam, nor
> your particular Tcl projects, but bras seems quite capable of handling
> complicated builds ...)
>
> Information on bras: http://wiki.tcl.tk/5975

Thanks. I've checked the wiki page on alternatives to make, and looked
at bras. I didn't think it was still active because the change log on
the web site lists the last release in 2002.

I need to build multiple tcl projects in addition to multiple c++
projects all rooted in different repositories, and I currently work with a
bat file doing this with a sledgehammer approach.

--
sheila

sheila miguez wrote:
>
> On Thu, 23 Dec 2004 09:39:39 +0100, Arjen Markus wrote: 
> 
>
> Thanks. I've checked the wiki page on alternatives to make, and looked
> at bras. I didn't think it was still active because the change log on
> the web site lists the last release in 2002.
>
> I need to build multiple tcl projects in addition to multiple c++
> projects all rooted in different repositories, and I currently work with a
> bat file doing this with a sledgehammer approach.
>

I suggest you give it a try: it has many possibilities to define the
rules for deciding when to compile and link. All the tools for C and C++
ought to be there (alas, none for Fortran, for which I would like to use
it and some compilers I suffer from require a host of options to work
properly; I ought to take that hurdle some day soon - it may be just
"cold-water fear" because I do have bits and pieces a-working).

Regards,

Arjen

In article <slrncslf4m.12u.she@ftupet.com>,
sheila miguez  <she@nospam.pobox.com.invalid> wrote:

Cameron Laird wrote:
>

> b.  .BAT and make are rather horrible, at
>     least in comparison to the maintenance
>     tools we developers deserve to have.

Defining these tools seems to be non-trivial, given
all the initiatives to create alternatives to "make"!

(I wish there was an off-the-shelf replacement for
"make" - bras may come close, but, like I said before, it
lacks a few things that I need ... and that may be the
reason for the plethora of make-like utilities ...)

Regards,

Arjen