[jamming] Alternatives to headerscanning - Axelsson, Andreas - com.perforce.jamming

6 messages in com.perforce.jamming[jamming] Alternatives to headerscanning

From	Sent On	Attachments
Axelsson, Andreas	20 Mar 2003 07:32
David Abrahams	20 Mar 2003 07:49
Diane Holt	20 Mar 2003 08:05
Axelsson, Andreas	20 Mar 2003 08:31
David Abrahams	20 Mar 2003 08:51
Axelsson, Andreas	21 Mar 2003 05:54

Subject:	[jamming] Alternatives to headerscanning
From:	Axelsson, Andreas (Andr...@dice.se)
Date:	03/21/2003 05:54:17 AM
List:	com.perforce.jamming

Yes, such an extension would definitely be useful. I'll look into how it could be done when I understand the syntax of Jam enough not to create anything non-standard. I suppose the GLOB command would be a good starting point.

/axl

-----Original Message----- From: David Abrahams [mailto:davi...@rcn.com] Sent: den 20 mars 2003 17:52 To: Axelsson, Andreas Cc: 'jamm...@perforce.com' Subject: Re: [jamming] Alternatives to headerscanning

"Axelsson, Andreas" <Andr...@dice.se> writes:

Ok, that sounds good, only in this case, some of my sources are binaries and pattern-matching may not work very well. In this specific case I'm looking at Maya 3D-files that include other Maya files that each include a number of .tga texture files. I'm not very familiar with grep and all the magic that it can do, so perhaps I'm wrong?

Hmm, that does sound like it might need a Jam extension. Maybe you could add a variable HDRCMD which specifies a command to run on the file and extract some text that's processed later. That sounds like it demands a primitive we've been wanting to add to Boost.Build for quite some time: "run this shell command and capture its output" (aka popen on Unix, I think). Unfortunately AFAIK writing a portable version of that primitive is nontrivial. If anyone already has it as a Jam extension, please let me know!