Smalltalk › Squeak › Squeak VM

VMMakerTool vs VMMaker file handling for VMMAker.oscog and a hunch

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

tty

VMMakerTool vs VMMaker file handling for VMMAker.oscog and a hunch

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

timrowledge

Re: VMMakerTool vs VMMaker file handling for VMMAker.oscog and a hunch

On 24-02-2014, at 10:15 AM, gettimothy <[hidden email]> 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; [hidden email]; http://www.rowledge.org/tim
After a number of decimal places, nobody gives a damn.

tty

Re: VMMakerTool vs VMMaker file handling for VMMAker.oscog and a hunch

Thanks Tim.

---- On Mon, 24 Feb 2014 10:24:07 -0800 tim Rowledge<[hidden email]> wrote ----

On 24-02-2014, at 10:15 AM, gettimothy <[hidden email]> 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; [hidden email]; http://www.rowledge.org/tim
After a number of decimal places, nobody gives a damn.