Transport Tycoon Forums

petert wrote:I'm afraid I can't upload the enable debug build because the exe is 70 mb. You will either have to keep using my builds or build yourself.

You could try uploading to mega upload or media fire or rapid share

Tomorrow, it's late now.

Hello

petert wrote:I'm afraid I can't upload the enable debug build because the exe is 70 mb. You will either have to keep using my builds or build yourself.

Whow, 70 MB, it's reasonable not to offer this build. My self compiled g40a1117b Cargodist build with debug has 34 MB (executable: 30.5 MB), as equation: a typical nightly build (downloaded Linux-generic binary) has around 10.4 MB (executable: 4.7 MB; both on GNU/Linux Ubuntu).

Tschö, Auge

Yes, thanks for understanding. I've never seen a 10MB Linux exe before, wow.

Also getting crashes with r18286_win32.

Could it be that te crashes happen cause i adjust existing scenarios ?? This time i only used 1 trainset grf, but still two Ship grf and two airplane grf...

Will try a game now with random build map.

And another crash, builded a random map this time.

These Windows crashlogs are utterly useless without a way to resolve the location to a line of source code. So for this bug to be 'uncovered' you need to make the binary with MSVC (not GCC) and post both the executable, the generated .pdb file and the crash.dmp.
Or in other words: debugging code generated by GCC on Windows without running an executable with debugging symbols outside of GDB is virtually impossible. So for Hamilton2007's crash reports to be useful someone needs to make MSVC binaries and not GCC binaries.

Rubidium wrote:So for Hamilton2007's crash reports to be useful someone needs to make MSVC binaries and not GCC binaries.

I've set up MSVC, but I cannot get it to compile. I will try again soon, sorry for all the worthless builds without proper crash reports.

I am going to be the "someone" for once: here is a MSVC debug build of latest cargodist diff. The PDB rar includes the openttd.pdb file. Please tell me if the build needs something else.

Edit: Build outdated.

Thank you Terkhen! May I ask what OpenTTD.pdb is?

The Debug symbols, I believe.

Are they always almost 5MB?

Is it normal that such a debug mode build makes the game to run much slower ??

That is to be expected.

Hamilton2007 wrote:Is it normal that such a debug mode build makes the game to run much slower ??

Yes, debug-builds often disable (some) optimisations that would make it harder to match generated code back to source code

Note: The trunk patch for CargoDist at this moment does not apply cleanly to trunk. Trunk_version.txt says r18325, but it has failed hunks.

I just checked out r18325 and applied the patch:
I don't get any rejects. petert, are you sure you haven't messed up your source tree again? Just keep a clean copy of trunk around and make copies whenever you apply patches. Or use git or mercurial for proper version management.

Personally, I would suggest Mercurial (HG) as it doesn't take so long to get a single revision.
Also, I find it's good working practice to always have a folder with un-changed trunk, and running svn update on it regularly. I then make copies of that to work on, rather than bothering the svn server so much. Plus it saves my bandwidth.

Gremnon wrote:Personally, I would suggest Mercurial (HG) as it doesn't take so long to get a single revision.
Also, I find it's good working practice to always have a folder with un-changed trunk, and running svn update on it regularly. I then make copies of that to work on, rather than bothering the svn server so much. Plus it saves my bandwidth.

Fonso, may I ask why you've chosen git? It's so much harder to use on Windows and it uses a ton of room with lots of un-needed folders and files.

Seeing how many branches fonso uses, I would expect that branches are the reason why. They are handled in git much better than in mercurial.