Re: Strongtalk: planning a way forward

Here is a link to the image (a file named strongtalk.bst and a
directory containing the source database).

http://www.sendspace.com/file/6ntz20

You should unpack it into the directory into which you have checked
out the gcc-linux branch.

The linux build files are found in the directory named 'build'. The
main makefile expects a command line argument ROOT_DIR which should
point to the directory that you checked out the branch into. The main
target is named 'default'. Upon a successful build this will generate
an executable named 'strongtalk' in the build directory.

To run the command line script you should start from the root of the
strongtalk checkout. Run a command similar to the following

build/strongtalk -f tools/strongtalkrc-forInterpretedTests -script
tools/test.dlt

test.dlt contains the Smalltalk code to run a basic set of tests
against the image. In theory at least, you should be able to use this
script to file code into the running image and then save the updated
version. Haven't tried it though.

On Nov 30, 5:45 am, Brian de Alwis <[email protected]> wrote:
> Thanks for replying Stephen.
>
> > The linux port is partial so far, but it does enough to run a basic
> > non-UI test from the command line. You will need an updated image to
> > run it. This has NOT been checked in (images are about 2M and the
> > current limit it 100M). Building this image requires a Windows
> > environment. Images are still built organically (grown!?); there is no
> > image bootstrap currently. It's one of the outstanding issues. If you
> > are interested I can upload a copy of the image and sources to
> > sendspace.
>
> Yes please.  Or you could just e-mail it to my [email protected]
> account.
>
>
>
> > There are many more aspects required to fully enable a linux port. The
> > os_linux.cpp module needs to be completed and a core to the UI needs
> > to be built.
> [...]
> > Not that I want to discourage anyone enthusiastic to get involved, but
> > it is my opinion is that porting to other OSes would be a distraction.
>
> I'm expecting very little changes from the Linux port to other Unix
> OSs.  Regardless, NetBSD's Linux emulation supports using the Linux
> toolchain and running Linux binaries.
>
> > We should certainly have some discussion on a widget set
> > to base the UI upon. Qt had been suggested at one stage, but nothing
> > has been built so far, so it's basically a blank canvas.
>
> Which will make sense once the VM is running smoothly.
>
> > My personal goal is to complete the Linux port.
>
> I'm happy to work to that goal.
>
> My interests in Strongtalk are to have a fast Smalltalk system
> suitable for experimenting with numeric computation.  The compile-
> debug-edit cycle of Java is just too painful, even with environments
> like Eclipse.  Getting Strongtalk to a full-fledged IDE not going to
> happen any time soon, but it's a goal to strive for.
>
> > Hope I haven't put you off too much.
>
> Not at all :-)  My plan then is to start playing with the gcc-linux
> branch, ask questions, and send any patches to this list.
>
> Brian.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---