JamieLei wrote:
With Overlord Rudge's help over IRC, I managed to compile it

- it plays fantastic - no errors at all!
I specifically just needed a version of CargoDist with Timetabling - this is the first one to come along since a release about 1 and a half years ago with CargoDist + 24h Timetables
Good to hear that. Would you be willing to share what went wrong so others can avoid it?
Also VVG extracted the 24h timetables from ITM. it seems to work nicely but I have not yet tried to merge it with the patchpack.
I do not yet know how it behaves with the daylenght patch(es).
Lord Aro wrote:
File comment: 7z compressing used to get it under forum limit
Orudge: please raise it!
Nah, more people should use 7z. It is free, does its job better and supports more formats then most other zippers do.
it is stripped (presumably), because i have no idea how to un-strip it
The above should do it but what is below is better and gives more info on crashes. (It will also make your executable much larger.)
On ubuntu 9.04 you can not use dpkg to build a debug build as I have found out some time ago. (debhelper is too old)
Configures debugging and compiles an unstripped binary (even if you did not use the configure command above).
Code: Select all
./configure --enable-debug=3; make
To check if it is indeed stripped (You can also check the size of the executable, 40.2MB with my latest code.)
Goes to executable inside gdb.
runs the debug build.
Command to enter in the terminal after a crash, without closing OpenTTD, to get much more info then you would get from an assert .
Shorter:
To start the debug build directly after compilation without checking first if it is unstripped:
Code: Select all
./configure --enable-debug=3; make run-gdb
To restart it after a crash while still in gdb: (do not forget "bt full" first, if you want a detailed back trace)
To run it afterwards after having quit gdb:
Credits to bluebottle for helping me with most of the above. (see page 6/7 of this thread.)
Also, you can still run OpenTTD by clicking the executable but you will not be getting the terminal output.
Thank you for the suggestion and the link Rubidium. I have seen the page before.
compile farm wrote:
For us to compile your branch/patch we need the following:
* An url to a VCS to check out the source from; one of the following:
o subversion
o mercurial (hg)
o git
* A location where we can copy, using scp, the resulting binaries and logs to. We do not post the custom binaries on our server!
* At least one developer that claims that the code doesn't do something obviously harmful.
* I do not have a repository to check out the source from at the moment. Nor do I have configured my pc to upload to a repository at the moment.
* I do not have a place to upload the binaries to.
* I do not have the intention to include potentially harmful code but I do not know what all included patches do in detail either. Although all of them are included manually.
I am missing two out of three requirements for the moment.
I could, of course, do some searching to see if I can find enough space somewhere. For free as my budget is limited and I am not allowed to host a server from my pc, I think. (and my upload speed is slooooooooow ...)