On 21 Nov 2013, at 12:30, Clément Bera <[email protected]> wrote:
> This mechanism does not work with Monticello. > > On my builds I have for this case something similar to: > > > ./pharo $JOB_NAME.image config $REPO ConfigurationOfMyProject > --install=bleedingEdge > ./pharo $JOB_NAME.image eval --save 'SmalltalkImage compilerClass: > OpalCompiler. Compiler recompileAll.’ Thanks, Clément, that works. I now do a ./pharo $JOB_NAME.image eval --save 'PEGParser recompile.’ so that OPAL picks up the options. > 2013/11/21 Sven Van Caekenberghe <[email protected]> > > On 19 Nov 2013, at 16:45, Sven Van Caekenberghe <[email protected]> wrote: > > >> > >> Yes, you can do it per class-hierarchy… you can implement on the class > >> side a method to parametrize the compiler: > >> > >> compiler > >> ^super compiler options: #(- optionInlineTimesRepeat) > > > > Thanks, Marcus, that works just great. > > Marcus, > > Are we sure this option mechanism works when loading code through Monticello ? > > I mean, this build fails the PEGParser tests: > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ > > but it includes the #compiler options in Xtreams-Parsing-nice.7 > > Could it not be that this is a chicken-egg problem: the #compiler options are > only there _after_ the class is loaded/compiled, or maybe it is an > instance/class side problem ? > > Sven > > >
