Dear Wolfgang,
thank you very much for this.
There are other compiler options not supported by ozmake either
(e.g., all the warning options like --warnshadow). Could we perhaps
add support for arbitrary compiler options in a generic way? For
example, we could have an option --compileroptionsfile=PATH, where
the text file at PATH contains arbitrary compiler options which are
all hand to the compiler by ozmake. Of course, the users are
responsible for what they are doing.
I thought a while about an option --compileroption=OPTION, where
OPTION is any compiler option and the option --compileroption could
occur multiple times. However, I couldn't come up with a suitable
format this late.. Easy cases would be boolean options like
--compileroption=warnshadow
However, I don't know how to handle compiler options which expect a
list of values...
--compileroption=environment=MODULES
BTW: any chance such changes to ozmake will make it into the main
repository?
Best
Torsten
On Sep 11, 2007, at 8:24 PM, Wolfgang Meyer wrote:
I created a patch for ozmake that makes it possible to use macros
in Oz code and still use ozmake to compile it.
It simply adds a new option "--environment" to ozmake and
propagates its value to the compiler.
Maybe this is useful for somebody else as well.
Best
Torsten
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
http://strasheela.sourceforge.net
http://www.torsten-anders.de
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
