Forget that, that file is the only one which is *already* in the build/ folder from the cog.tar, which I trashed when restarting the procedure.
One more gotcha... Phil 2013/2/16 Camillo Bruni <[email protected]>: > You use the wrong configuration in VMMaker (thanks to the strange naming > conventions > this happens way too easily) :/ > > I think you can just use Pharo.*Config instead of Cog.*Config? > > On 2013-02-16, at 15:18, "[email protected]" <[email protected]> wrote: > >> And inside the app, there is a CogVM executable, not a pharo one. >> >> Confused I am. >> >> Phil >> >> 2013/2/16 Camillo Bruni <[email protected]>: >>> >>> On 2013-02-16, at 14:30, "[email protected]" <[email protected]> wrote: >>> >>>> Well, this is the script from hell... >>>> >>>> newImage.sh doesn't executes the last line: >>>> >>>> # >>>> ---------------------------------------------------------------------------- >>>> # try to open the image... >>>> set -e >>>> openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" >>>> rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; >>>> openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" >>>> >>>> >>>> because openImage exits the script... >>>> >>>> Question: can't we run all of this headless? >>> >>> >>> yes please ;) I guess I never fully tested it under unix/win and nobody >>> really used it >>> besides me. >>> >>> => run everything in headless mode >>> => use the zeroconf scripts >>> >>> >>> >> > >
