Chill's patchpack v14_7

[NekoMaster]

I can't afford to download the stuff to compile win32 builds

What "stuff" is that? The MSYS guide doesn't require many things - if it still works.

Im still on windows 7, so MSYS doesnt work on windows 7 for some reason :\

[petert]

Im still on windows 7, so MSYS doesnt work on windows 7 for some reason :\

OK - but that's not what you said originally.

[NekoMaster]

Im still on windows 7, so MSYS doesnt work on windows 7 for some reason :\

OK - but that's not what you said originally.

I know, but from what I read its like your suggesting i use it, and I can't (all the computers here use windows 7)

[Rubidium]

I can't (all the computers here use windows 7)

That's exactly where Microsoft "Invented" the lovely Windows XP Mode for.

[NekoMaster]

I can't (all the computers here use windows 7)

That's exactly where Microsoft "Invented" the lovely Windows XP Mode for.

And its also what will cause the one paying for my internet to rip my head off.

[Scautura]

I can't afford to download the stuff to compile win32 builds

What "stuff" is that? The MSYS guide doesn't require many things - if it still works.

Im still on windows 7, so MSYS doesnt work on windows 7 for some reason :\

Rubbish... Unless you've got something strange up with your machine(s), MingW and MSYS work fine on Win7 - I would know, given that I'm running Win7 x64, developing a game (compiled with MingW), and compiled a version of Chill's Patchpack (you can download it up there somewhere) with MSYS/MingW.

I would be willing to bet that there are other issues causing problems (administrator rights?) which are causing issues.

[NekoMaster]

Rubbish... Unless you've got something strange up with your machine(s), MingW and MSYS work fine on Win7 - I would know, given that I'm running Win7 x64, developing a game (compiled with MingW), and compiled a version of Chill's Patchpack (you can download it up there somewhere) with MSYS/MingW.

I would be willing to bet that there are other issues causing problems (administrator rights?) which are causing issues.

Nope, Im the admin, Im running Windows 7 Ultimate 32bit. Last time Petert tried to help me it MSYS didn't work, it worked one my other pc (which is dead now) that had Windows XP
No one in my house uses Windows XP anymore.

[petert]

And its also what will cause the one paying for my internet to rip my head off.

What are you talking about? Does your ISP really try to spare a few hundred mbits of bandwidth?

[NekoMaster]

And its also what will cause the one paying for my internet to rip my head off.

What are you talking about? Does your ISP really try to spare a few hundred mbits of bandwidth?

Somehow we're paying like, 100 dollars for internet every month or more, and we have a 30 dollar plan (3mbps/25GB). Somehow we keep going over our limit and its really starting to p*** my step mom off... btw I have Rogers S**t-Speed Internet

[ColdIce]

Santa Claus is coming to town

enjoy!

compile log http://www.heypasteit.com/clip/L06

[Arie-]

...

Somehow we're paying like, 100 dollars for internet every month or more, and we have a 30 dollar plan (3mbps/25GB). Somehow we keep going over our limit and its really starting to p*** my step mom off... btw I have Rogers S**t-Speed Internet

Totally offtopic, but if you're always over your limit why: don't upgrade your subscription or use a bandwidth monitor.

[ChillCore]

Thank you for the build ColdIce.

I just have two little questions if I may.
- When you bumped the source, have you adjusted projects/openttd_vs100.vcxproj ?
For your build it is not that important but before posting the matching source it is. I was going to attach the bumped version to the first post but I have posted the version against r20026 for the moment to be safe.
- If it is not to much trouble could you rename the bins you post to chipp_v?_rxxxxx.rar in the future? This to make sure people are not confused and mistakenly take it for an official release.
When I download a compiled binary I rename it automatically to what it is but after sitting there for a while (next to other compiled versions) one may forget what exactly they have downloaded and only seeing the reversion number does not help very much.

Also thank you for the compile log.
Seems like I have a few minor things to fix in the more height levels patch.

ps:
Santa is early this year.
Ho ho ho

[ColdIce]

i just downloaded head revision with turtoise and applied the patch, nothing more. r20033 its a type mistake. actually is 20030. and sure i can rename it that, no trouble at all.

[ChillCore]

Thank you for the information.

Just for your information and I have not checked if it could be the case here ...
Sometimes when you checkout a certain revision the revision number ingame is not increased.
eg. If you checkout r19929 the revision number ingame will say r19925 as r19926 to r19929 are backports to the 1.0 branch and do not alter trunk, but when you pull a diff it will say r19929.

[bluebottle]

Ah, finally got my machine upgraded to Ubuntu 10.04.

So, this is a build of r20026 for Lucid Lynx, using Chillcore's great patch pack.

• As with the distro OpenTTD package, you need to have the data files in /usr/share/games/openttd/data/.
• This build is unstripped to provide better (i.e. useful) core dumps/backtraces. This is similar to including the .pdb file for MSVC builds.

Download: openttd_chillcore-r20026M-no_debug-unstripped-i386.deb

[ChillCore]

Thank you for the build bluebottle.
I have tried building my own debug build following your instructions but it did not work for me somehow.
However following instructions posted by Rubidium in the Infrastructure Sharing thread I managed to build one anyway.
See codeblock.

Code: Select all

./configure --enable-debug=3
make run-gdb
bt full     <-After crashing

[bluebottle]

Thank you for the build bluebottle.
I have tried building my own debug build following your instructions but it did not work for me somehow.
However following instructions posted by Rubidium in the Infrastructure Sharing thread I managed to build one anyway.
See codeblock.

Code: Select all

./configure --enable-debug=3
make run-gdb
bt full     <-After crashing

You're welcome.

I'd be interested to know where the build process failed for your unstripped build. Do you find that the enable_debug=3 build is slow? Mine ran at 10 fps when I tried that option, and the binaries were huge, IIRC. The enable_debug parameter just reduces gcc's optimizations, which makes the resulting binary easier to work with and reduces the number of possible factors that can cause a crash. But it makes the binary run very inefficiently.

Code: Select all

        if [ $enable_debug = 0 ]; then
                # No debug, add default stuff
                OBJS_SUBDIR="release"
                if [ "$os" = "OSX" ]; then
                        # these compilerflags makes the app run as fast as possible without making the app unstable. It works on G3 or newer
                        CFLAGS="-O3 -funroll-loops -fsched-interblock -falign-loops=16 -falign-jumps=16 -falign-functions=16 -falign-jumps-max-skip=15 -falign-loops-max-skip=15 -mdynamic-no-pic $CFLAGS"
                else
                        if [ "$os" = "MORPHOS" ]; then
                                CFLAGS="-I/gg/os-include -noixemul -fstrict-aliasing -fexpensive-optimizations -mcpu=604 -fno-inline -mstring -mmultiple $CFLAGS"
                                LDFLAGS="$LDFLAGS -noixemul"
                        fi

                        CFLAGS="-O2 -fomit-frame-pointer $CFLAGS"
                        LDFLAGS="-O2 -fomit-frame-pointer $LDFLAGS"
                fi
        else
                OBJS_SUBDIR="debug"

                # Each debug level reduces the optimization by a bit
                if [ $enable_debug -ge 1 ]; then
                        CFLAGS="$CFLAGS -g -D_DEBUG -D_FORTIFY_SOURCE=2"
                        if [ "$os" = "PSP" ]; then
                                CFLAGS="$CFLAGS -G0"
                        fi
                fi
                if [ $enable_debug -ge 2 ]; then
                        CFLAGS="$CFLAGS -fno-inline"
                        LDFLAGS="$LDFLAGS -fno-inline"
                fi
                if [ $enable_debug -ge 3 ]; then
                        CFLAGS="$CFLAGS -O0"
                else
                        CFLAGS="$CFLAGS -O2"
                fi

What does the output of "file <your executable>" say for the enable_debug build? I'm mainly interested in whether you have an unstripped binary (you probably do). This is what I get:

Code: Select all

$ file /usr/games/openttd 
/usr/games/openttd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

[ChillCore]

Below is the output why it failed with dpkg.

Code: Select all

~/test_chipp_7$ mv os/debian .
~/test_chipp_7$ export DEB_BULD_OPTIONS=notrip
~/test_chipp_7$ dpkg-buildpackage -rfakeroot -uc -us -t
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package openttd
dpkg-buildpackage: source version 1.1~svn-0
dpkg-buildpackage: source changed by Matthijs Kooijman <matthijs@stdin.nl>
dpkg-buildpackage: host architecture i386
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 7.0.50)
dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: warning: (Use -d flag to override.)

As I mentionted before I am missing some stuff. (debhelper is not new enough or to new?)
Second try with with -d flag:

Code: Select all

~/test_chipp_7$ dpkg-buildpackage -rfakeroot -uc -us -t -d
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package openttd
dpkg-buildpackage: source version 1.1~svn-0
dpkg-buildpackage: source changed by Matthijs Kooijman <matthijs@stdin.nl>
dpkg-buildpackage: host architecture i386
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   dh_clean
 dpkg-source -b test_chipp_7
dpkg-source: info: source format `3.0 (quilt)' discarded: no orig.tar file found
dpkg-source: info: using source format `1.0'
dpkg-source: warning: source directory 'test_chipp_7' is not <sourcepackage>-<upstreamversion> 'openttd-1.1~svn'
dpkg-source: info: building openttd in openttd_1.1~svn-0.tar.gz
dpkg-source: info: building openttd in openttd_1.1~svn-0.dsc
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
Unknown option --prefix=/usr
dh_auto_configure: command returned error code 256
make: *** [build] Fout 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

With --enable-debug=3; make run-gdb; openttd.exe is 38.5 MB
I do have five more patches in that build than in v7.

Code: Select all

file bin/openttd
bin/openttd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

Yes, it is slower than normal,mainy on startup, but that is to be expected.
Once fired up it runs reasonably. I use coopsavegames most of the times for testing my build.
How do I check framerate?

In case your interested, I know you are , my clean trunk debug build is 32.1 MB.

[bluebottle]

Code: Select all

~/test_chipp_7$ export DEB_BULD_OPTIONS=notrip

This is your first issue: the command should read "export DEB_BUILD_OPTIONS=nostrip"

Code: Select all

dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 7.0.50)

As I mentionted before I am missing some stuff. (debhelper is not new enough or to new?)

Yes, you must get this fixed, there's no point in proceeding because you won't get a result. I remember that you
once said you were running an older version of Ubuntu, so here is how you can check if you have debhelper installed,
and what version it is:
run "dpkg -l debhelper".

I have version 7.4.15ubuntu1. If you don't have it, install it with "apt-get install debhelper". If it is too old (<7.0.50), sorry, you have to upgrade your Ubuntu installation.

With --enable-debug=3; make run-gdb; openttd.exe is 38.5 MB
I do have five more patches in that build than in v7.

Code: Select all

file bin/openttd
bin/openttd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

Yes, it is slower than normal,mainy on startup, but that is to be expected.

It will depend on hardware specs, of course, my machine is almost five years old, so I need the optimizations.
The main thing is that the executable is unstripped - without that the backtrace from gdb is practically unusable because
there are no symbols for it to give you. AFAIK, the debug options will not help you with backtracing from crashes - they are
only there to help debug compiler or platform problems.

Another point is that you don't need to run "make gdb-run" every time if you already have an unstripped executable. You can
run any executable inside gdb with:
"gdb executable-name-here"
and then typing "run". Use "bt full" after the crash. It's quicker than having to use the make process every time.

Once fired up it runs reasonably. I use coopsavegames most of the times for testing my build.
How do I check framerate?

Don't know the answer to that one, sorry. There isn't any console command for it. My 10fps figure was a guesstimate.

[ChillCore]

Code: Select all

~/test_chipp_7$ export DEB_BULD_OPTIONS=notrip

This is your first issue: the command should read "export DEB_BUILD_OPTIONS=nostrip"

Hawk eyes you have Yoda says.
But the result remains the same after correcting typos.

run "dpkg -l debhelper".
I have version 7.4.15ubuntu1. If you don't have it, install it with "apt-get install debhelper". If it is too old (<7.0.50), sorry, you have to upgrade your Ubuntu installation.

Hmm? Strange result? Or should I ignore the first few lines?

Code: Select all

*********-desktop:~$ dpkg -l debhelper
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Naam           Versie         Omschrijving
+++-==============-==============-============================================
ii  debhelper      7.0.17ubuntu4  helper programs for debian/rules

When trying to re-install it says I allready have the newest version.

Which brings me to my next two questions.
If/when I upgrade my Ubunbtu install to 10.4 will I still be able to use the binaries I have compiled with 9.04?
Also while searching for answers to my first question I have seen some reports about issues with NVIDEA drivers with newer Ubuntu. Are those already solved?
Not having satisfying answers to both issues have kept me from updating until now.

ps:
Thank you for your time and patience bluebottle, much appreciated.