Am 10.01.2012 18:40, schrieb Joshua Cranmer:
> make -f client.mk configure &> $conferr
> if [ $? != 0 ] ; then
> submitError "Error configuring $name" $conferr
> exit 1
> fi
>
> # Since we trashed the objdir, we need to add these myrules.mk back in
> # [this is needed for IDL support]
> pushd $objdir
> for f in $(find -name 'autoconf.mk'); do
> echo '-include $(DXRSRC)/xref-tools/moztools/myrules.mk' >>
> ${f/autoconf/myrules}
> done
> popd
>
> # Clean up any old .csv files, particularly those generated by configure
> find $objdir -name '*.csv' | xargs rm
This bit was most helpful, thanks a lot. I added a special case for that
- a shame to add project-specific bits but it's at least isolated. Might
make sense to allow including snippets from extra files for that.
>> Feedback still welcome of course. If I'm assuming too much to my
>> specific setup, please point it out.
>
> To me, the biggest issue is that there may want to be more steps.
> Eventually, I think there needs to be the following:
> 1. Update source code
> 2. Configure the tree
> [ Clobber generated files from configure ]
> 3. Run some post-configuration steps (for Mozilla code, we want to stuff
> some things in myrules.mk)
> 4. Build the tree
> 5. Run some post-build steps (e.g., code-coverage)
> [ Generate index ]
> 6. Move results elsewhere
>
> I think all of the numbered steps probably want commands to do them
I sort of had a mostly automated build in mind so far. You wouldn't need
that script if all you wanted was to update the sources (1) and nothing
else. The one case I did include was the opposite, you can skip that
update. And it probably makes sense to let you skip ahead to the indexer.
Running something like 'make check' after the build would allow you to
replace the build bot I guess. It's a bit tricky as we'd need to move
the .csv files out of the way before running it. In fact it's the same
as with the extra configure step above as I think about it, except we
can't simply remove the files.
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
