That is a bit odd. Have you tried compiling with clang for both the compile and link steps? There's some clang-specific stuff in the configure script so it ought to work.Valle wrote:I had to escalate this problem to a friend from outside of the OpenTTD community, who provided me with the following solution.
Problem: OSX Mavericks and newer ships with several versions of the standard library libc++
Solution: entering the following code into the terminal window in which OpenTTD is compiled afterwards.I have attached the Mac OS X build of your patchpack I generated after that.Code: Select all
export LDFLAGS="-stdlib=libstdc++ -lstdc++"
I'm a little hesitant to add that to the configure scripts at the moment as I don't want to accidentally break any other combinations of toolchains/platforms which may not be affected at present, especially when I can't test anything Apple-related.
That is a bit baffling. Interestingly 21395 is 11 times 1945 which suggests some sort of scaling issue somewhere. Do you get the same issue on OpenTTD trunk? Are you using an increased day length?Valle wrote:Interestingly, there is a problem with the year display, which also exists with my friend's bundle.
If I'm in the year 1945, OpenTTD displays the year 21395. This problem persists in later years, with the year count rising accordingly.
Valle wrote: My build (attached below) doesn't display the version/build correctly in the main menu, just calling the version "norev000". I wasn't able to test it properly yet.
The OpenTTD build system runs the script `findversion.sh` which tries to work out what the version string should be.archy wrote:Wow, awesome selection of patches!
Also great to see someone do a patch pack "the proper way", with git branches. Hopefully this means it won't bitrot quite as fast as previous patch packs.
PS: I'm trying to build version 0.2.1 directly from https://github.com/JGRennison/OpenTTD-patches/releases but it prints this warning at the start:
Is this to be expected? Is there some way the configure script can be told the correct version number?Code: Select all
WARNING: there is no means to determine the version. WARNING: please use a subversion, mercurial, or git checkout of OpenTTD. WARNING: you can only join game servers that have been compiled without WARNING: version detection. WARNING: there is a great chance you desync. WARNING: USE WITH CAUTION!
If there's a file named ".ottdrev" it uses that, otherwise it looks to see if you're in an SVN, Mercurial or Git repository and looks at the current revision/branch/status etc. to get a version string.
I'm guessing that you downloaded a zip rather than `git clone`ing the repository, as this would not include the version info.
The zip files on Github are auto-generated, and I'm not sure how I could feasibly manually add version info to them (at least not in a way that isn't overly awkward). I'll have to think about how to modify the version detection script and/or add version info to tagged versions to do something else to work out the version.
The diffs in the first post have the version info added by the script I use to generate the diff.
Edit: This ought to be fixed as of v0.3.0.
