Oolite Bulletins

DaddyHoggy wrote:

The zipped development environment package I uploaded in the first post should contain all you need to build the game. You don't need any Local_XXXX file anymore. Just stick with the instructions in the first post in this thread and ignore the wiki ones.

Kind of negates the point of the wiki does it not - are people coming across Oolite for the first time more likely to find the BB or the wiki? (genuine question - I don't know)

another_commander wrote:

You are absolutely correct, DH. The wiki instructions should be replaced with the new ones, but unfortunately I cannot access the wiki from my normal internet connection. I will try to do it if and when I get the chance. If anyone else can get there before me, feel free to update the page. All that is needed is a copy/paste from the first post in this thread (maybe reformatted for wiki, of course).

another_commander wrote:

The zipped development environment package I uploaded in the first post should contain all you need to build the game. You don't need any Local_XXXX file anymore. Just stick with the instructions in the first post in this thread and ignore the wiki ones.

I have to note though, that if you have problems starting MSYS with GNUstep 1.15.3 and it works OK with the latest GNUstep version, then you will have to install the newest GNUstep and make sure that the environment sees only that last version. Just renaming the original gstep1153 folder to something else should be sufficient to make the old GNUstep disappear as far as the build environment is concerned, but you will have to ensure yourself that the new GNUstep has been setup correctly.

wades wrote:

What's sdl-config?

sdl-config is a shell script that returns settings of the SDL library, regarding the way SDL was built and what parameters are required for using its resources in other projects. Other libraries may have similar scripts in the /usr/local/bin MSYS folder. As an example, if you go to the MSYS propmt and execute 'sdl-config --version', it comes back with '1.2.13', if you execute 'sdl-config --libs' it returns the line that needs to be used for a successful linking of the library, something like '-L/usr/local/lib -lmingw32 -lSDLmain -lSDL -mwindows'. The returned value can be passed directly to makefiles and in this way you don't have to remember what the library needs for linking or where its headers are etc. Try executing 'sdl-config --help' for a list of options.

another_commander wrote:

If you have built the exe with the latest GNUstep, then you need the newest gnustep-base dll in the oolite.app folder. What are the contents of the oolite.app folder you are trying to run the exe from?

 c:/oolite-build/GNUstep/Local/oolite/trunk/oolite.app:
  total used in directory 10637 available 617654588
  drwxrwxrwx   1 wades    root             0 02-19 22:04 .
  drwxrwxrwx   1 wades    root             0 02-19 22:03 ..
  drwxrwxrwx   1 wades    root             0 02-19 22:04 GNUstep
  drwxrwxrwx   1 wades    root             0 02-19 22:04 Logs
  drwxrwxrwx   1 wades    root             0 02-19 22:02 Resources
  -rw-rw-rw-   1 wades    root        320000 02-19 22:02 SDL.dll
  -rw-rw-rw-   1 wades    root        315392 02-19 22:02 SDL_mixer.dll
  -rw-rw-rw-   1 wades    root       3940352 02-19 22:02 gnustep-base-1_15.dll
  -rw-rw-rw-   1 wades    root        858592 02-19 22:02 js32.dll
  -rw-rw-rw-   1 wades    root        922112 02-19 22:02 libiconv-2.dll
  -rw-rw-rw-   1 wades    root        280576 02-19 22:02 libpng14.dll
  -rw-rw-rw-   1 wades    root       1082908 02-19 22:02 libxml2-2.dll
  -rw-rw-rw-   1 wades    root         68608 02-19 22:02 objc-1.dll
  -rwxrwxrwx   1 wades    root       3047936 02-19 22:02 oolite.exe
  -rw-rw-rw-   1 wades    root             0 02-19 22:04 stderr.txt
  -rw-rw-rw-   1 wades    root             0 02-19 22:04 stdout.txt
  -rw-rw-rw-   1 wades    root         55808 02-19 22:02 zlib1.dll

another_commander wrote:

The three steps you mention are correct, but I cannot be certain that they will work first try. Changing gnustep-base is not trivial and once you switch to it the rest of the steps might or might not work. You will just have to try and see. There is no need to uninstall or scrap anything you have done so far, just rename temporarily gstep1153, msys_x, svn-win32-1.4.3, install the environment again and checkout Oolite in a different folder. If you want to return to your previous setup you can delete the three dev environment "new" folders, give the old ones their original names back and fall back to the original checkout of Oolite's source. Having multiple source checkouts is not a problem, as long they are kept separated from eachother.

I apologize for not being able to be more specific, but I do not have access to a 64-bit system to test my theory properly. If you want, PM me and we can give it a try over the [url=irc://irc.oftc.net/oolite-dev]#oolite-dev[/url] channel on irc.

Kaks wrote:

Wades, this might well be a red herring, but the javascript dll is specifically compiled for 32 bits windows, so it might cause some problems...

Cmd. Cheyd wrote:

another_commander wrote:

If I am not mistaken, Screet is building on 32-bit, then runs it on different, 64-bit system. At least, that's what I remembered from the last time he posted about this.

This is how I am doing it. IIRC, if I build directly on Win64 (Vista x64 Ultimate, 6GB Ram), MinGW opens 127 windows (command prompts actually), throws an error, then closes all 127 as the process crashes.

another_commander wrote:

{ big snip }

Instructions on how to build an Oolite trunk executable from zero:

IMPORTANT: The zip file you downloaded must be unzipped maintaining all paths under the root folder of the D drive (D:\).

This is the only catch with the package. Due to the way GNUstep sets up its paths by using absolute references, it is not possible to have this package working from any other drive. Since I am using my D drive to build, all this fun is set up to work from that drive letter only. You can change any drive's letter to D by following instructions as provided by Microsoft Support here.

Once unzipped, you must run the msys.bat file, found in D:\msys_x\1.0. You can create a shortcut to desktop for this file if you want. Once run, the environment will start up.

{ more snip }

if EXIST bin\nul cd bin
if EXIST rxvt.exe goto startrxvt
if EXIST sh.exe goto startsh

if EXIST bin\nul cd bin
rem if EXIST rxvt.exe goto startrxvt
if EXIST sh.exe goto startsh

      0 [main] sh 4784 sync_with_child: child 6968(0x144) died before initialization with status code 0x0
     81 [main] sh 4784 sync_with_child: *** child state waiting for longjmp
sh: fork: Resource temporarily unavailable
sh-2.04$

Kaks wrote:

The last time I successfully set up a build environment (the one I currently use) I followed my own advice:

https://bb.oolite.space/viewtopic.php?p=69755#p69755


I had to use the 'local' file, the build environment kept throwing errors without those files , and instead of .19 I used gnustep-core-0.22 & gnustep-system-0.22 which can be found on the same ftp server as their 0.19 counterparts.

Sorry to hear about the snafu with the 500GB disk, I've had something similar happen to me (managed to rescue some data from mine though) not too long ago. Not the best feeling in the world, to put it mildly.