topotto wrote:
> Hi, I am new to gst. I've just build binaries on windows using mingw, all
> went right just doing configure and make ... wonderful!!
Cool!
> as a next step I would like to install binaries on another windows machine
> but I was not able to understand how to do it. apparently it is not enougth
> to copy *.exe and *.dll to the other machine, can you please provide me
> suggestion on how to deploy gst on a new window machine?
First of all, if you haven't done it so far, you should do "make
install" to get a standalone install directory. You can then copy this
directory to a new Windows machine. The problem then is that currently
GNU Smalltalk is not "relocatable": the prefix in which it is installed
must be the one given in the configure invocation. Fixing this is one
of my priorities.
The idea of relocatable programs is that you configure with a fake
prefix, and then the package will be able to find its files whatever
directory you deploy the package in. Under Windows, the strategy is
usually to deploy everything in a single directory; under UNIX systems
instead you use a path in /opt, or your home directory.
When GNU Smalltalk will become relocatable, the suggested configure
invocation for Windows using something like this:
./configure --prefix=/nonexistent --bindir=/nonexistent \
--libdir=/nonexistent --with-image-dir=/nonexistent \
--with-pkglibdir=/nonexistent/modules --datarootdir=/nonexistent
Then, all the files will be installed in the same directory, and the GNU
Smalltalk installation will look more or less like a normal Windows
application.
Under Linux, you will use normal ./configure (actually "./configure
--prefix=/nonexistent" is better) and the package will automatically
become relocatable.
> I am also very interested in using gst to serve seaside applications, can
> you point out the potential plus of gst vs squeak in this area?
The pluses are that: 1) it is easier to deploy GNU Smalltalk images
because they are naturally headless (on the other hand, they are harder
to debug for the same reason); 2) it is easier to strip out unwanted
packages from GNU Smalltalk images because you can just reload your
files in a fresh image.
Paolo
_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
Locked
