Mac Binary Release

[jackoverfull]

Does anyone know any AI that will work on the OS X version?

?
KAi and AAI works fine for me.

[revcompgeek]

Well, I found evidence of an old patch that moved those symbols from internal code to external code, but no external code was used to replace the symbols. I put them back and it compiled but now I am having problems with the UnixFileSytemHandler. When run from the command line, I get:

Code: Select all

spring/trunk/rts/build/xcode/../../System/Platform/Linux/UnixFileSystemHandler.cpp:101: failed assertion `writedir && writedir->writable'
Abort trap

And splitting that assert into two asserts tells me it is the writedir not the writedir->writable that is the problem. I had to modify the code a bit to get some of the filesystem stuff to compile, but I might have messed it up.

Also, If I update svn, will it overwrite all my changes to the source, or will it let me merge them somehow?

[Tobi]

Well, I found evidence of an old patch that moved those symbols from internal code to external code, but no external code was used to replace the symbols. I put them back and it compiled but now I am having problems with the UnixFileSytemHandler. When run from the command line, I get:

Code: Select all

spring/trunk/rts/build/xcode/../../System/Platform/Linux/UnixFileSystemHandler.cpp:101: failed assertion `writedir && writedir->writable'
Abort trap

And splitting that assert into two asserts tells me it is the writedir not the writedir->writable that is the problem. I had to modify the code a bit to get some of the filesystem stuff to compile, but I might have messed it up.

Probably Spring didn't have permission to write to any directory in the search path. Though I thought that'd give an error not a failed assert.

Also, If I update svn, will it overwrite all my changes to the source, or will it let me merge them somehow?

No, it will let you merge them (or rather, it will automerge as much as possible and only when it can't it will set files to status "conflicted", and put markers in it to mark which sections conflicted. You then have to resolve these conflicts manually, remove the markers and mark the file as resolved.)

However, if you did a lot of modifications and you are unsure whether you'll be able to fix any conflicts easily, it may be a good idea to make a backup first anyway. Without backup there is not an easy way to put your working copy in the state it was in before the update (with conflicts).

[Boaal]

Does anyone know any AI that will work on the OS X version?

?
KAi and AAI works fine for me.

With which mods?

[jackoverfull]

balanced annihilation (and some others too).

[AF]

bump

[Sharkey]

I would like to get Spring working on OS X. I have an Intel Macbook Pro that has XCode installed.

I think to start we need to gather all the OS X developers and we need to work together instead of in separate silos.

I am planning to collaborate with AF, and I hope that all other OS X developers collaborate with us.


Sharkey

[AF]

I just want all the details in one place so I know what needs doing whats already done and what problems there are. I lack the time to actively maintain the mac port, but Id like to chip in every now and again and test, and help out here and there. Whatever work does get doen needs to eb done in SVN.

Also has anybody looked into the prospect of Mac OS X buildbots?

[Sharkey]

I just want all the details in one place so I know what needs doing whats already done and what problems there are.

Everyone,

I have created a Google group "Spring on OS X". The purpose of the group is to provide a repository of information for Spring OS X developers.

I encourage all OS X developers to join the Google group, so that we can start collaborating together and finally get Spring on OS X.

The group URL is http://groups.google.com/group/spring-on-os-x


Sharkey

[Tobi]

I'm not sure separating mac development from "real" development is really the way to go: I don't think many non-Mac developers will follow this discussion group for example. (I won't, I have enough things to keep track of already.) As such, they won't be able to help you.

Please just ask questions (on this forum, in the lobby or on IRC, #sy at QuakeNet or #taspring at FreeNode) or search this forum or the wiki if you need information: there is a hell of a lot information out there, it may be a little hard to find at times, but that's why you can ask

For example, the dependencies of Spring for building from source with scons are easily distilled from the following instructions in the wiki:

sudo aptitude install scons build-essential zlib1g-dev libfreetype6-dev
sudo aptitude install libsdl1.2-dev libopenal-dev libglew-dev libboost-dev
sudo aptitude install libboost-thread-dev libboost-regex-dev libdevil-dev
sudo aptitude install libboost-serialization-dev python2.5-dev zip
sudo aptitude install libvorbis-dev libxcursor-dev

Also it might be an idea to try get in contact with elio and possibly krysole, who did earlier work on a Mac port. Elio should still have some patches lying around, I think, and Krysole was working on the branch krysole-texture sometime, to - if I recall correctly - fix texture loading on the Mac.

[Tobi]

Also has anybody looked into the prospect of Mac OS X buildbots?

When the build process actually works on Mac and there are instructions somewhere, just give me ssh access to a 24/7 on Mac OS X box, then I can set up a build slave.

[AF]

I dont mind leaving my macbook somewhere on while Im at work but i cant guarantee 24/7 and I dont know how I would set up SSH on it either.

[Tobi]

24/7 doesn't have to be 100%, would work if it's up most of the time. Without SSH however you'll need to configure build slave yourself (actually I prefer that, in particular if you don't ask any questions about it )

In either case first mac team must have determined and documented how to build spring.., I'm not going to set up buildbot and at same time fix buildsystem for Mac etc.

[AF]

As I understand it the problem is mainly an issue with dependencies at the moment. As I remember, DevIL wouldn't build under mac but someone said something perhaps on the google group?

[jackoverfull]

24/7 doesn't have to be 100%, would work if it's up most of the time. Without SSH however you'll need to configure build slave yourself (actually I prefer that, in particular if you don't ask any questions about it )

In either case first mac team must have determined and documented how to build spring.., I'm not going to set up buildbot and at same time fix buildsystem for Mac etc.

i have a mac server that is up almost 24/24/7, if needed i can configure it as a build bot.

But, as you just wrote, we must before _build_ it.

i succeded in building devil some months ago, it is definitively buildable on mac os x.

[AF]

We need to build a 'Maclibs' package just like the 'vclibs' for visual studio, aimed at x86 Mac OS X.

If you can provide a suitable DevIL library...

Someone should also maintain a checklist of what we have and dont have

[jackoverfull]

We need to build a 'Maclibs' package just like the 'vclibs' for visual studio, aimed at x86 Mac OS X.

why only x86? spring runs on ppcs too├óÔé¼┬ª

If you can provide a suitable DevIL library...

Someone should also maintain a checklist of what we have and dont have

i can try, but not until some days.

[BrainDamage]

why only x86? spring runs on ppcs too├óÔé¼┬ª

a) ppc architecture for macs is deprecated
b) ppc builds will only sync against ppc unless all endianess and other architecture differences will be debugged & fixed
c) only tiny fraction of macs nowdays is ppc

a + b + c together makes it simply not worth it, and more time it will pass, the less worth will be

[jackoverfull]

why only x86? spring runs on ppcs too├óÔé¼┬ª

a) ppc architecture for macs is deprecated

not yet. apple will still support it for a while.

b) ppc builds will only sync against ppc unless all endianess and other architecture differences will be debugged & fixed

i hope that someday this will happen. Anyway├óÔé¼┬ªbetter than nothing!

c) only tiny fraction of macs nowdays is ppc

Not so thin├óÔé¼┬ª

[AF]

You have a PPC mac don't you?

Well I think for the moment it would be best to do x86 only then once that's working we can look at the task of endian-ness and PPC cpus. Porting spring to a new OS is one thing, but another cpu architecture is a different ballgame. For all we know PPC may never sync with x86 no matter how hard we try even fi we fix all the endian issues.