From: Larry Evans (cppljevans_at_[hidden])
Date: 2005-06-10 16:38:49
On 06/10/2005 03:35 PM, David Abrahams wrote:
> Disclaimer: I didn't write this stuff and I've never run it.
Fair enough. Thanks for the help though.
> Larry Evans <cppljevans_at_[hidden]> writes:
>>I've also searched the pp.py file for clues by searching for 'template';
>>however, that wasn't much help either.
> Why would you expect to find 'template?'
Because I was under the mistaken assumption that the python code,
somehow was the only step in generating the files. Now I'm guessing
that the preprocessing done by preprocess.cmd does most of the work
and the python code does some minor adjustments. I'm guessing that
the only reason for the python code is to save the user from having to
regenerating the code with the preprocessor each time he compiles.
IOW, the code in aux_/preprocessed is sort-of a cache or somewhat
like a pre-compiled header.
>>I'd appreciate any other suggestions for a linux user ;)
> I would:
> change the script to write '#!/bin/sh\n' into the beginning of
> preprocess.cmd when not on Windows
> change the script to set the mode on "preprocess.cmd" to +x after
> writing it
> change the os.system call to say "preprocess.cmd"
I did something like that, as you can see from my other post. However,
instead of naming the script file, preprocess.sh, I renamed it
preprocess and invoked it with:
cpp = os.path.join(".","preprocess")
os.system( "%s %s %s %s %s" % ( cpp, boost_root, mode, file,
file_path ) )
I'm guessing that windows will not mind if cpp is ".\preprocess" instead
of just "preprocess".
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk