Peter Tanski wrote:
darcs sent on behalf of Simon Marlow:
* Add first cut of the validate script
A ./validate
I don't mean to quibble when you are stuck in managerial drudgery but
overwriting build.mk:
validate:7-11
if [ -f mk/build.mk ]; then
mv mk/build.mk mk/build.mk.bak
fi
echo BuildFlavour=quick >mk/build.mk
cat mk/build.mk.sample >>mk/build.mk
means I can't have configure copy build.mk.msvc to build.mk for
Windows-native and use validate to test. (This isn't a problem: I want
to do things right.) Would you rather I set build.mk.msvc stuff as a
conditional Make block at the end of config.mk.in, i.e.,
ifeq "$(TargetOS_CPP)" "windows"
< a whole boatload of extra settings >
endif
That would be better yes. I'm curious to see what the "boatload of extra
settings" are - there might be a better way to approach this.
P.S. For configure args, how about using arguments to validate? For
example:
validate powerpc-apple-darwin
--> ./configure <nothing>
validate i386-unknown-windows
--> ./configure --target=i386-unknown-windows <or> --target=$1
If you like that idea I'll send an implementation of it.
The other option we want to pass to validate is how many processes to run in
parallel. So I suppose validate should have a little command-line parser, and
there should be syntax for options to give to configure. I don't particularly
mind what the syntax *is*, escpecially if someone else is writing the patch :-)
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
