189 replies to this topic

[wraitii]

I'm really not sure that the third feature is compulsory.

[fcxSanya]

wraitii, on 24 February 2012 - 09:28 PM, said:

I'm really not sure that the third feature is compulsory.

Apple promise that it is not:
http://www.apple.com...n/security.html :

Quote

You control what you install.
<...>Gatekeeper brings you even more security options<...> Or you can install all apps from anywhere, just as you can today. You can even temporarily override your setting by Control-clicking, and install any app at any time.<...>

[historic_bruno]

Was doing a bit more digging and discovered this list of where App Store apps are allowed to write files. Note even ~/Documents is not listed, if we "manage" pictures we should use ~/Pictures, but we really don't so even that could be debated. Clearly saved games would have to go somewhere in ~/Library. It's very restrictive and I think it would be a good idea to follow those guidelines as general rules even if we don't plan to be on the App Store (for those curious, there are potential licensing conflicts between GPL and Apple's App Store policies).

------

Some people may have noticed you can't build 0 A.D. anymore even if you install Xcode and MacPorts. The reason is that GCC is no longer included with Xcode and the command line build tools have been removed by default from Xcode 4.3. If you installed an earlier version, as I did, it should work even if you upgraded. This annoyed a lot of people and caused some havoc among developers.

Just recently Apple has released a standalone package called "Command Line Tools for Xcode", which includes LLVM-GCC (it pretends to be GCC) and all the libraries needed. It's a free ~160MB download from the Apple Developer Downloads site. You need a free Apple ID to access it. Or if you have Xcode 4.3+, you can download the same package through Xcode Preferences.

I've tested, and it's possible to build the game and all its dependencies with only that package, in place of Xcode. However, because no SDKs are provided for backward compatibility, it's not possible to build a practical bundle without Xcode. Anyway I'm modifying the build scripts to handle either situation.

[Sonarpulse]

Oh Apple. Is there any other *nix that's more of a pain in the @#$%?

Somebody made something similar for 10.6 (I read that "Command Line Tools for Xcode" is only for 10.7): http://kennethreitz....d-homebrew.html & the package itself https://github.com/k...-gcc-installer/

[historic_bruno]

Sonarpulse, on 25 February 2012 - 09:14 PM, said:

Somebody made something similar for 10.6 (I read that "Command Line Tools for Xcode" is only for 10.7): http://kennethreitz....d-homebrew.html & the package itself https://github.com/k...-gcc-installer/

Quite right and apparently that was the inspiration for Apple releasing their own package, but as 10.6 is older than 1-2 years, they obviously feel no need to support it Of course if someone is on 10.6, they can install an older Xcode and get the command line tools installed.

[Sonarpulse]

will your script work with 10.6? Also, I always had the impression that the difference between 10.5 and 10.6 was less, if because nothing more than because "leopard" and "snow leopard". Is that at all true?

[historic_bruno]

Yeah, it should work fine on 10.6. I think we could support 10.5 with some hassle, but it's not something I'm pursuing, maybe once all the dust settles someone in the community will work on that

[wraitii]

There are only slight compatibility issues between Leopard and Snow Leopard, which was a 20$ minor "major update" of the system, mainly to streamline everything. It was massively adopted, so supporting 10.5 has no reason to be a priority.

[Sonarpulse]

Good to know, thanks both of you.

[Echelon9]

historic_bruno, any updates on the Mac build scripts? I'd love to give it a try out, and it would help my development on 0ad to have a consistent way to roll binaries.

[historic_bruno]

Well yes, they've been updated. It's not easy to share though, since it involves moving and renaming things (maybe easier if I used Git?) Anyway that stuff will have to wait until after Alpha 9, I'll probably be helping review existing patches in the meantime. I would like to upload an official OS X bundle for Alpha 9 on LatestReleaseMac.

[Sonarpulse]

Yes! getting an official, stable binary out will be a HUGE step forward. And of course, using this method will also help reach the ultimate goal of "easy" mac compilation.

[historic_bruno]

I "upgraded" to Xcode 4.3, it's nice because unlike earlier versions (I was using 4.1) there's no need to install it, you just run the app bundle directly. Apparently updates are deltas now instead of requiring massive 2GB+ downloads. Want to uninstall? Drag the app to the trash. This means that all the Xcode required files are bundled, including SDKs. Unfortunately this causes problems if scripts are looking for SDKs in the old /Developer/SDKs location. Prime example: Boost build scripts. They try to be clever and provide a simple "macosx-version" option that automatically searches directories in /Developer/SDKs for a match. So it works great with Xcode 4.2 and earlier, but suddenly breaks on Xcode 4.3 with an unintuitive error:

error: "10.6" is not a known value of feature <macosx-version>
error: legal values:

See any mention of /Developer/SDKs or anything else remotely useful? I was shocked that a package like Boost misbehaved this way. Hope they've fixed it for 1.49, but either way my script has to set CFLAGS and LDFLAGS manually for Boost.

I also had to update my build scripts, SDKs are now located in... wait for it... /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs.

After that it works fine. Xcode detected that I had installed the "Command Line Tools for Xcode" package and didn't ask me to download them again. I did have to fix one Premake-related build error (11259) that only occurred with the new command line tools.

[Sonarpulse]

was "Command Line Tools for Xcode" modified for Xcode 4.3? i.e. should the scripts still work with the latest version of the CLI package?

[historic_bruno]

You can download the "Command Line Tools for Xcode" either in Xcode preferences, or separately as mentioned above, but it's the exact same package. As far as I know the scripts will continue working since the errors and most of the deprecation warnings have been fixed.

[Sonarpulse]

Awesome!

[historic_bruno]

OS X package for Alpha 9 is now available at http://trac.wildfire...atestReleaseMac

[memmaker650]

historic_bruno, on 15 March 2012 - 07:53 PM, said:

OS X package for Alpha 9 is now available at http://trac.wildfire...atestReleaseMac

Thank you for your great work. Downloading.

I will test the game under mac and will tell here all the thing or bug i detect in the game.

Thanks another time.

[Geek377]

historic_bruno, on 15 March 2012 - 07:53 PM, said:

OS X package for Alpha 9 is now available at http://trac.wildfire...atestReleaseMac

Thanks so much man, you just saved me a ton of time
It works great in Snow Leopard (10.6.8)

[memmaker650]

historic_bruno, on 15 March 2012 - 07:53 PM, said:

OS X package for Alpha 9 is now available at http://trac.wildfire...atestReleaseMac

Game works fine on my MBP 4,1 from 2008 with Snow Leopard 10.6.8 and 4Gb of RAM. 80% of CPU used during game execution.

Game runs fluently, no sound (normal i know developers are changing the sound system to put it right with OpenAL), no apuses and the games menu runs smoothly and right.