www.perforce.com/jam/jam.html

After 3 years, jam 2.3 is out to replace jam 2.2.

This is not a major release, but includes a number of user-contributed
changes from the Perforce Public Depot, as well as bug fixing and
enhancements done at Perforce Software.

The complete release notes are at 

	http://public.perforce.com/public/jam/src/RELNOTES

The highlights are:

	Jam code is now ANSI C, so it can be compiled with a C++ 
	compiler, but no longer with a K&R compiler.

	Experimental support for rules returning values.

	Miscellaneous bug fixes.

	Lots of porting changes.

This release is being made in anticipation of more agressive development
of Jam in the next few months.  I wanted to get what we had out so that
any user-contributed development can then be more easily merged.

The starting page for Jam information is:

	http://www.perforce.com/jam/jam.html

Enjoy!

www.perforce.com/jam /jam.html

We (Scale8) are shortly going to move to Jam.  

I was wondering what the wish list is for jam?  You mention aggressive
development; what new features are you planning?

-----Original Message-----
From: Christopher Seiwald [mailto:seiwald <at> perforce.com]
Sent: Friday, January 05, 2001 12:07
To: jamming <at> perforce.com
Subject: [jamming] ANNOUNCE: jam 2.3 available at
www.perforce.com/jam/jam.html

After 3 years, jam 2.3 is out to replace jam 2.2.

This is not a major release, but includes a number of user-contributed
changes from the Perforce Public Depot, as well as bug fixing and
enhancements done at Perforce Software.

The complete release notes are at 

	http://public.perforce.com/public/jam/src/RELNOTES

The highlights are:

	Jam code is now ANSI C, so it can be compiled with a C++ 
	compiler, but no longer with a K&R compiler.

	Experimental support for rules returning values.

	Miscellaneous bug fixes.

www.perforce.com/jam /jam.html

I'm happy that development has restarted on Jam.

I have a few questions about the just announced release ...

I did not see in the release notes that my
patch to handle the new AIX 3.4 ar format was applied.

I also did not see mention of the regular expression stuff 
done by Paul Haffenden.

The problem with LOCATE on library's and library members
(they must be the same or Jam fails) was not mentioned.

Was the bug about grouping fixed:

TESTVAR = Hello ;
if $(TESTVAR) && ($(TESTVAR) != $(TESTVAR)) 
{
}

Do we (the Jam users at large) need to resumit 
which patches/bugs/etc ?

Finally, what are these planned enhansements, and 
do you need any help.

Randy

> -----Original Message-----
> From: Christopher Seiwald [mailto:seiwald <at> perforce.com]

www.perforce.com/jam /jam.html

Several have written with comments and questions about the jam 2.3 release.

I should have been more emphatic: jam 2.3 includes only SOME of the user
contributed changes.  What got left behind?  Anything done after September,
as that is when I last pulled in changes submitted to the public depot,
the variable substitution using regular expressions, as that went too
far in a direction ($(X:do-everything)) I'm trying to re-evaluate, and
some things no doubt I simply missed.

Development of Jam has never really stopped, though it slowed and all
of what was done was kept internal to Perforce.  This release was to
push things out the door, so that user contributions can come from
similar code.

Jam does not have a full-time curator.  As some of you may know, I have
other responsibilities at Perforce that take my time.  We are looking
to hire an open source curator, for both Jam and other projects here.
I still plan to control its direction (which remains lean and mean, in
case you're wondering), but its the machinations that take considerable
effort.

Still, the best way to get changes into Jam is to submit them to the
public depot.  Eventually, I plan to incorporate all changes or send
email explaining why the change is not being incorporated.

As to what's being planned, here are the crib notes:

	-       a directory scan operation, like

			files = [ glob $(SRCDIR) *.c ] ;

multi-project build

Hi
I have following structure of my projects:
Proj1 -|
	 |-ProjWatcom
		|-Jamfile
	 |-ProjUnix
		|-Jamfile
Proj2- |
	 |-ProjMSVCNT
		|-Jamfile
Tools-
	 |-Jambase
		|-bin.linuxx86
			|-jam
		|-bin.ntx.86
			|-jam
	 |-Jambase
	 |-Jamrules

My task  is to create jamfiles in such way,
that I will be able to compile different environments (LINUX,NT,WATCOM)
using the same Jambase and Jamrules
My problem is to define TOP. I know that TOP is a directory that has the
Jamrules
How I can create any pointer from my jamfiles to the TOP directory that
contains my Jamrules?

Thx

Ivetta Estrin-Sandler

jam crash

The attached file causes a crash on Windows NT 2000, and MPW. (Unmapped
memory excpetion).
(I've tested with 2.3, and that one contained the error too.)

Can anyone reproduce this?
I used:
jam -fki.txt
Or is there something illegal with the file?

Regards,
Miklos

LFLAGS =
"somethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethingsomethi"
; 

alma = "somethingsomethingsomethingsomethingsomethingsomething" ; 

ECHO "Begin" ;
LFLAGS = "$(LFLAGS) $(alma)$(alma)" ;
ECHO "End" ;

ECHO "Begin" ;
LFLAGS = "$(LFLAGS) $(alma)$(alma)" ;
ECHO "End" ;

EXIT ;

Re: jam crash

I imagine that it is just generating a macro that is too big. We had to 
up the macro string size once...

dave

  > From: Miklos Fazekas <boga <at> mac.com>
  > Reply-To: Miklos Fazekas <boga <at> mac.com>
  > References: <200101062000.MAA09441 <at> frankenrouter.perforce.com>
  > Date: Mon, 8 Jan 2001 16:12:52 +0100
  > MIME-Version: 1.0
  > Content-Type: multipart/mixed;
  > 	boundary="----=_NextPart_000_0011_01C0798D.DA85DF10"
  > X-Priority: 3
  > X-MSMail-Priority: Normal
  > X-Mailer: Microsoft Outlook Express 5.50.4133.2400
  > X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
  > Sender: jamming-admin <at> perforce.com
  > Errors-To: jamming-admin <at> perforce.com
  > X-BeenThere: jamming <at> perforce.com
  > X-Mailman-Version: 2.0beta2
  > Precedence: bulk
  > List-Id: Discuss the build tool Jam/MR with other users <jamming.perforce.com>
  > 
  > The attached file causes a crash on Windows NT 2000, and MPW. (Unmapped
  > memory excpetion).
  > (I've tested with 2.3, and that one contained the error too.)
  > 
  > Can anyone reproduce this?
  > I used:
  > jam -fki.txt

Re: jam crash

----- Original Message -----
From: "Dave Lewis" <dlewis <at> vignette.com>
To: <boga <at> mac.com>
Cc: <jamming <at> perforce.com>
Sent: Monday, January 08, 2001 6:03 PM
Subject: Re: [jamming] jam crash

> I imagine that it is just generating a macro that is too big. We had to
> up the macro string size once...
>
> dave

I was not aware of this limit. (Probably 1024 then.)

I see, so instead of generating on long LFLAGS like:
LFLAGS = "$(LFLAGS) $(newflag)" ;
I should generate it into a list:
LFLAGS += $(newflag) ;

Thank you very much!

Regards,
Miklós.

www.perforce.com/jam /jam.html

> As to what's being planned, here are the crib notes:
> 
> -       a directory scan operation, like
> 
> files = [ glob $(SRCDIR) *.c ] ;
> 
> That would populate the $(files) variable with the .c
> files in $(SRCDIR).

Here's a simple 'glob' command for jam 2.3. The syntax is
    glob DIR PATTERN PATTERN ...
The pattern matching uses the builtin glob() function.

I added this to the end of compile.c.
------------------------------------------
#include "filesys.h"

static LIST *_glob_pat;
static LIST *_glob_list;

/* Callback to file_dirscan() */
static void glob_func(
 char *file,
 int status,
 time_t t )
{
 FILENAME f;
 LIST *l;

 file_parse( file, &f );

Multiple Depnedants and order of actions.

I have the following jam-file, and the files:
a,b,c,d,e

actions copy
{
echo "copy $(<) " > $(<)
}
rule copy
{
DEPENDS $(<) : $(>)
}
actions copy2
{
echo "copy $(>) " > $(<[1])
echo "copy $(>) " > $(<[2])
}
rule copy2
{
DEPENDS $(<) : $(>) ;
}

copy a : c ;
copy2 a b : d ;
copy b : e ;

DEPENDS all : b a ;
NOTFILE all ;

If i edit the file 'c' and 'e'. The orders of actions will be: