Guillaume Laforge wrote
> Are the optimization flags hard-coded?
> CompilerConfiguration has those get/setOptimizationOptions, but also
> get/setJointCompilationOptions, as well as other ones like
> get/setCompilationCustomizers, get/setScriptExtensions,
> get/setScriptBaseClass, and so on.
> Those
On Wed, Aug 7, 2013 at 7:02 PM, Peter Niederwieser wrote:
> Guillaume Laforge wrote
> > Isn't there a way to specify parameters that are part of
> > CompilerConfiguration's API?
>
> I'm not aware of a way. There is support for setting arbitrary optimization
> options, if you mean that.
>
Are the
Guillaume Laforge wrote
> Isn't there a way to specify parameters that are part of
> CompilerConfiguration's API?
I'm not aware of a way. There is support for setting arbitrary optimization
options, if you mean that.
Cheers,
Peter
--
View this message in context:
http://gradle.1045684.n5.nab
Isn't there a way to specify parameters that are part of
CompilerConfiguration's API?
I thought it was the case.
On Mon, Aug 5, 2013 at 11:40 PM, Peter Niederwieser wrote:
> Guillaume/David,
>
> there isn't currently any support for `--configscript` in Gradle. (It may
> be
> worthwhile to mentio
Guillaume/David,
there isn't currently any support for `--configscript` in Gradle. (It may be
worthwhile to mention that Gradle generally integrates with the Groovy
compiler via the latter's API, not via the command line.) If you want to see
it supported, please submit an idea and explain your use
Good question!
Worth asking as well our Gradle friends in CC.
Guillaume
On Mon, Aug 5, 2013 at 6:38 AM, David Clark wrote:
> Does anyone know if gradle supports the --configscript option for
> compiling groovy code? The docs suggest it doesn't support that option,
> but I'm hoping I'm wrong.
