Oolite Bulletins

It seems that oolite source build (from pristine sources) needs to download a file first: http://jens.ayton.se/oolite/deps/firefo ... s-only.tbz
I wonder if it's possible to include that archive (or its content) directly into oolite sources.

Or maybe it would be better to provide instructions on where to obtain the file and where to place it, so that it's picked up by the build. That's so that the build itself doesn't require network connectivity.

Or maybe tweak oolite to not require that file. As I understand it contains Mozilla JS engine which gets compiled into oolite. Maybe oolite could use the JS engine from some standard (external) package like e.g. spidermonkey (or libxul).


P.S. I am building oolite 1.76 package for FreeBSD from the source archive.

Hi and welcome. The SpiderMonkey for Oolite has to be built specifically for the game and the external file is therefore required. As per the file ExternalLibrariesSourceCodeChanges.txt in the Doc folder the differences with respect to the "normal" JS are:

3. SpiderMonkey v1.85 (all platforms)

- Specific build settings for Oolite are required. Library rebuilt with the following macros defined as shown below:
JS_THREADSAFE defined on Mac and Linux debug builds.
MOZ_TRACE_JSCALLS defined in order to enable full JavaScript profiling."

Can the original file from here https://developer.mozilla.org/en/SpiderMonkey (http://ftp.mozilla.org/pub/mozilla.org/ ... 0.0.tar.gz) be used in place of the file that is currently being used?

BTW, the described changes do not seem to be needed for release package building. They seem more like development/debugging feature. But maybe I am just confused.

Just in case, here's my WIP version of update of the FreeBSD port to 1.76:
https://redports.org/browser/avg/games/oolite

agapon wrote:

Just in case, here's my WIP version of update of the FreeBSD port to 1.76:
https://redports.org/browser/avg/games/oolite

Looks good. I'll try building it later tonight.

Also, nice to see a fellow daemon.

Edit:
*mutter mutter*
echo "GNUSTEP_WITH_CLANG=yes" >> /etc/make.conf
*grumble humping gcc42 filthy something something*

Glad to meet you!

I have these in my make.conf.
GNUSTEP_WITH_GCC46=yes
WITH_GNUSTEP_DEVEL=yes

I read it somewhere that latest oolite doesn't work with the older GNUstep (1.19) and indeed oolite gave an error with that.
With 1.22 it works fine.