Hi All.
I noticed that VMMakerTool burps on the oscogvm/platforms file path (on linux) while the scripting approach uses that just fine. (Moving all the subdirectories under osgocvm/ to ./ let's the tool do its thing just fine).
My hunch is that scripting is the preferred way to build and VMMakerTool is not used for .oscog
True?
I just want to be sure for documentation purposes.
thx.
tty
On 24-02-2014, at 10:15 AM, gettimothy gettimothy@zoho.com wrote:
Hi All.
I noticed that VMMakerTool burps on the oscogvm/platforms file path (on linux) while the scripting approach uses that just fine. (Moving all the subdirectories under osgocvm/ to ./ let's the tool do its thing just fine).
My hunch is that scripting is the preferred way to build and VMMakerTool is not used for .oscog
True?
IIRC Eliot doesn’t use the UI tool. I did update it a smidge last year to make it work with the way code was layed out then; it probably needs another firkle to deal with the latest tree shape.
The VMMakerTool was always just a way to drive the scripting side of the VMMaker anyway. For any sort of automation, scripts are the way to go.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim After a number of decimal places, nobody gives a damn.
Thanks Tim.
---- On Mon, 24 Feb 2014 10:24:07 -0800 tim Rowledge<tim@rowledge.org> wrote ----
On 24-02-2014, at 10:15 AM, gettimothy <gettimothy@zoho.com> wrote:
> Hi All. > > I noticed that VMMakerTool burps on the oscogvm/platforms file path (on linux) while the scripting approach uses that just fine. (Moving all the subdirectories under osgocvm/ to ./ let's the tool do its thing just fine). > > My hunch is that scripting is the preferred way to build and VMMakerTool is not used for .oscog > > True?
IIRC Eliot doesn’t use the UI tool. I did update it a smidge last year to make it work with the way code was layed out then; it probably needs another firkle to deal with the latest tree shape.
The VMMakerTool was always just a way to drive the scripting side of the VMMaker anyway. For any sort of automation, scripts are the way to go.
tim
vm-dev@lists.squeakfoundation.org