Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[senior_javier_de_laminar]

Hi guys,

I've been playing the December 2010 binary release of LCS on Windows XP by Jonathan for the past few weeks. Following the forum post link, I did a check-out of the latest trunk revision (r483) from the Sourceforge SVN repository and built it on my Mac. The build is clean; however, the binary I got out of the process corresponds to a different version than the latest binary release. The title screen indicates "v3.11.3svn Maintained by the Open Source Community". I can also only launch the game from the Terminal after changing to the top-level trunk directory, otherwise I get a message about missing sitemaps.txt and various XML files.

Can someone tell me whether the Sourceforge files reflect the "state of the art"? Is there a different repository? Does Jonathan have a different repository?

Thanks and cheers,
Senior Javier de Laminar

[Carlos Gustavos]

Yes, the Sourceforge files are the latest development. The title screen says the same thing for me and I moved the binary to not get the error messages, but it is still the latest in development.

[senior_javier_de_laminar]

Yes, the Sourceforge files are the latest development. The title screen says the same thing for me and I moved the binary to not get the error messages, but it is still the latest in development.

I take it then that Jonathan just modified the version number on the title screen on the latest binary release? Maybe he can give me his 2 cents... I'm asking because I would like to be able to compile and play the same version on my Mac, but the "v3.11.3svn" title confuses me.

[Kay12]

Use Wine if you want to be sure you get the same treats as Windows users.

[Janus]

The Windows build uses the PACKAGE_VERSION defined in the C++ source in includes.h. I just did a text search for "3.11.3svn" and found it in the configure.ac file. I assume the Mac compile process is using that configuration file to define the PACKAGE_VERSION. I'd assume the fix would be to either update that version number as well, or remove it from being declared there so that it will use the one defined in includes.h. The latter would probably be lead to easier maintenance, assuming (perhaps wrongly) that it doesn't mess up the compile process for Mac/Linux.

[Jonathan S. Fox]

I'm glad Janus had an idea of what was going on, since I don't really. I wasn't the person that set up the Mac/Linux build tools,  so I'm not super clear on how to get everything working properly.

[senior_javier_de_laminar]

Thanks everyone for the replies!