Jam and static source checks. Any advice?
David Hoogvorst <dc.hoogvorst <at> inter.nl.net>
2002-04-01 18:48:35 GMT
I'm quite new to jam, but quite enthousiastic I should say, and try to
change the build system at my work to jam. Now, we have a home-made system
merely based on jam, but with a lot of Perl and Ruby scripting around it.
We develop software since 1982, so in the whole system parts are in Fortran,
parts in C and parts in C++. Furthermore, a lot of code is generated with
Pascal tools and Perl and Ruby scripts, due to (inter)nationalization needs
in the Fortran bit. The whole codebase is about 10,000 files I guess.
What we do, is that while developing (on NT or W2000), one has a local copy
of the module in a working directory. (We don't use the MS Visual
environment or anything like that). The rest of the sources remain in the
repository. Whenever one tries to build, his sources are put through a
number of static checks (line length, diacritic symbols, lint), to avoid as
many problems as possible when porting the software to the platforms we do:
OpenVMS, AS/400, IBM Mainframe, most Unixes (Unices?), and NT/W2000.
I've been struggling getting my jambase right. What I want to do first, is
to get the sources through these static checks. These checks are all command
line tools that exit with nonzero if not succesful. Furthermore, they yield
What I want is the following: If the static check is successful, remove all
the report files. If the static check fails, leave the report files and stop
the build (or leave a clear message where the build started to go wrong).
Jam cleans up when things go wrong, and leaves no trace, so that's just the
opposite of what I want.
Furthermore I wonder how I should go about with this local work directory.