Many posters have issues building their own executables and/or paksets. I hope to bring some light into this dark with a quick guide on building PakBritain128-Extended on Linux and Windows.
Linux users:
Clone the github repository following the guide here (https://help.github.com/articles/cloning-a-repository/) and the command
git clone https://github.com/jamespetts/simutrans-pak128.britainYou may need to install libpng15.so.15 from here (http://ftp.altlinux.org/pub/distributions/ALTLinux/Sisyphus/x86_64/RPMS.classic//libpng15-1.5.28-alt2.x86_64.rpm), by extracting the /usr/lib64/ contents into your /usr/lib/ and the /usr/share/ into your /usr/share/.
In your cloned directory, .../simutrans-pak128.britain/ run
make -jX X is the amount of threads (or cores) your cpu has plus one (i7 2700K (4 cores) 8 threads = 9).
There may be an error encountered which requires the installation of build essentials (Error 126, "sudo apt-get install build-essential"). If you encounter Error 127 you can try running make with sudo.
This is an
old guide to compiling your own pakset on Windows.
- Install Python from here (https://www.python.org/downloads/), I would go for 2.7.10 but this is open to your preference.
- Install the MakeObject Script Engine from here (http://sourceforge.net/projects/moscript/).
- Download a fresh copy of PakBritain from GitHub (https://github.com/jamespetts/simutrans-pak128.britain), the branch (above the file list) is currently "half-heights" as of May 2015. Extract this to a folder like in step 2 above.
- Download the Extended Makeobj.exe from here (http://bridgewater-brunel.me.uk/downloads/Simutrans-Experimental.zip). You will only need makeobj.exe and can move it into the PakBritain folder.
- Find "makeALL.mos" in the main folder and edit the file with Notepad or similar. Replace config config "makeobj=%makeobj%" with "makeobj=makeobj.exe".
- Run "makeALL.mos".
- Wait for the script to complete, which usually takes a few minutes. While it does that, download the folders for inside the completed pak from here (http://ul.to/xn24r6zx).
- When the script has finished, copy/move the "Pak128.Britain-Ex-0.9.X", from within original folder you extracted the GitHub sources in, to your previously compiled Simutrans Extended game folder.
- Extract the folders for inside the completed pak from two steps ago into the "Pak128.Britain-Ex-0.9.X" folder.
- Start Simutrans.exe to check whether the pak runs.
Thank you to jamespetts, VS, and all others in the project.
Splendid, thank you - stickied!
There is no need to use sudo. In general make shoud never be run as root, except for "make install". The compilation should run for security reasons as normal unprivileged user.
Vladki: I get Error 126 or 127 if I try to compile without sudo. This is probably due to file ownership issues which I'm still quite foreign to. I've edited the post to reflect this.
In this case no part of the process (git clone; make) shall be run with sudo. So you should be the owner of those files. However it is possible that the files are marked read-only. You can fix that by running:
chmod -R u+rwX .
In the cloned directory. If it fails on some files, check the ownership with "ls -l"
Ah, and of course if you once had run "sudo make", some files will be owned by root. Just delete them as root "sudo rm" and try again.