[squeak-dev] No vm-display-x11 Plug-in After Building From Source
On FreeBSD 10.1
B J
quarterwavevertical at gmail.com
Tue Dec 16 05:15:57 UTC 2014
<snip>
> If you think that the module is not being built at all, take a look at the
> config.h
> file in your build directory. That is the output of the cmake configure
> process,
> and if there is some issue related to locating the build libraries, you will
> probably
> see evidence of it in config.h. Look for definitions that are commented out,
> but
> maybe should not be.
Nothing that I might recognize stood out for me.
>
> Note, the "so.xxxx" naming convention is part of the installation process,
> so
> don't worry about that. If you can build the VM and install it, the naming
> will
> take care of itself.
>
> I'm not sure which source package you are starting with, but here is a
> simple
> recipe for building the latest from Subversion.
>
> 1) Start with an empty directory, then get the latest versions of all the
> platforms sources and the VMMaker generated sources:
>
> $ svn co http://squeakvm.org/svn/squeak/trunk/platforms
> $ svn co http://squeakvm.org/svn/squeak/trunk/src
>
> 2) In that same directory, make a subdirectory in which to build the VM:
>
> $ mkdir build
> $ cd build
>
> 3) Copy the attached Makefile into your build directory.
It wanted to install a 64-bit version. I haven't attempted to edit to
file for 32 bits.
>
> 4) build the VM, and install it if you get plausible results.
>
> $ make
> $ sudo make install
I used:
/root/Desktopo/squeak/platorms/unix/cmake/configure
followed by:
make
make install
I got the same results as before, though there was a squeakvm.core
file in my build directory as a result of the crash.
There is a vm-display-X11 directory in my build directory, but when I
open it, there's a directory named "CMakeFiles". Inside that, is
"vm-display-X11.dir" and, going further, it looks like its a
continuing series of nested directories.
>
> This makefile is what I use on Linux, so you may need to fiddle around with
> the
> CFLAGS, or add additional "--without xxxx" options to exclude modules that
> give
> you problems, but otherwise I think it should work.
I haven't tried that yet, partly because I don't know enough about
what's going on.
The mystery continues.
<snip>
More information about the Squeak-dev
mailing list
|