Gump had one severe limitation: it only created its scanners in the CURRENT directory regardless of where the compiled Oz file was supposed to be written. Ideally, it should be the case that Gump creates its files in the destination build directory.  It was not obvious to me whether this could be done easily with the current design.  So, I am checking in a workaround: if you set Property 'oz.gump.directory', that's where Gump will create its files.  This property can be set from the compiler's command line using the new --gumpdir option.
Gump had one severe limitation: it only created its scanners in the CURRENT
directory regardless of where the compiled Oz file was supposed to be written.
Ideally, it should be the case that Gump creates its files in the destination
build directory.  It was not obvious to me whether this could be done easily
with the current design.  So, I am checking in a workaround: if you set
Property 'oz.gump.directory', that's where Gump will create its files.  This
property can be set from the compiler's command line using the new --gumpdir
option.

LEIF: if there is a simple way to do the right thing, i.e. create Gump files
in the destination build directory, please do it or give me some hints.  I'd
much rather that it be done right.  This workaround is embarrassing.



mistasse/mozart-graal,eregon/mozart-graal,mozart/mozart2,eregon/mozart-graal,eregon/mozart-graal,eregon/mozart-graal,eregon/mozart2,yjaradin/mozart2,mistasse/mozart-graal,mistasse/mozart-graal,mozart/mozart2,mozart/mozart2,Angeldude/mozart2,dianacgr/mozart2,layus/mozart2,dianacgr/mozart2,eregon/mozart-graal,mistasse/mozart-graal,avisparesearch/Mozart2,dianacgr/mozart2,Angeldude/mozart2,eregon/mozart-graal,mistasse/mozart-graal,Angeldude/mozart2,avisparesearch/Mozart2,layus/mozart2,yjaradin/mozart2,layus/mozart2,yjaradin/mozart2,eregon/mozart2,eregon/mozart2