Ok. Seems to be ready. Xcode project is generated. All features are supported. Packaging to .dmg is done. Looking forward to see changes in trunk.
osx.path - dl.dropbox.com/u/1777581/osx.patch
osx.diff - dl.dropbox.com/u/1777581/osx.diff
dependency.zip - dl.dropbox.com/u/1777581/dependency.zip
Patch applied, rev 3018
Iāve made a dmg package (rev 3019) so it could be added to download section on main page - dl.dropbox.com/u/1777581/vcmi-0.90-Darwin.dmg
Thank you for contribution!
By the wayā¦ How is that includes are platform specific? I see CBattleAnimations.h included in CBattleInterface.h ā why is it needed?
Iām not sure if it belongs there, it is r3019, not the actual VCMI 0.9. Besides, Iām not sure how to label it or whether it needs some additional instructions.
How about creating a wiki page āInstallation on OS Xā with download link and instructions just like we have wiki.vcmi.eu/index.php?title=Ins ā¦ n_on_Linux ? [Or, if thereās little difference, we could make it a single page for both Linux/OS X.]
You can edit vcmi wiki after signing in with your forum account. 
To tell the truth I donāt know myself Maybe itās a sign of Clang immaturity. Maybe something else. But in some places forward declarations havenāt worked so I replaced them with direct includes.
Iāve already have draft āBuilding VCMI on OS Xā but Iām waiting for my new SSD to arrive soon. Iām going to install fresh system on it anyway so it would be a great possibility to check everything one more time on a clean system.
What about end-user installing itās really dead simple. Every OS X user will do it. The only problem is game data which anyway should be obtained separately and placed to ā~/.vcmiā. Iām a bit concerned about it because for myself I installed Heroes3 + WoG on Windows machine, compressed to zip archive and copied to Mac. Not sure itās a good solution because some people donāt have second computer with Windows. We have the same problem on Linux so maybe we need shared āPreparing game data on non-Windows systemā page. Any ideas? Because Wine based manual is not very best solution from my point of view.
Strange thing is that I use clang as well. And I donāt need those includes.
The only difference I can think of is standard library (libstdc++ for me, libc++ on Mac) but it shouldnāt affect includes either.
Yeah. Iāve been asked about this multiple times. Check my wiki update (vcmibuilder script):
wiki.vcmi.eu/index.php?title=Ins ā¦ aring_data
Will commit the script to svn today so you can check how it works on Mac. Shouldnāt be a problem - it requires bash itself + some optional utilites to extract data (wget, unzip, unshield, innoextract).
EDIT: done. Script uploaded, revision 3022
sourceforge.net/apps/trac/vcmi/b ā¦ cmibuilder
Yep, Iām using libc++ because libstdc++ on OS X is way outdated (from gcc 4.2). And I canāt use libstdc++ from newer gcc installed from MacPorts because of portability.
Yeah, unshield install seems to be working fine after some patches to unshield itself. Can anyone provide me iso with InnoSetup install to test innoextract?
Nevertheless vcmibuilder script seems to be working on OS X itās probably not a best option because you still need to compile from source both unshiled and InnoExtract (for some reason there is no InnoExtract in MacPorts, and unshield in MacPorts is too outdated). So Iāve decided to create a nice gui version of vcmibuilder script with prebuilt unshield and innoextract for OS X to make things as simple as possible once again. Here is patch for it:
dl.dropbox.com/u/1777581/vcmi/o ā¦ lder.patch
Donāt like increasing number of OS-specific filesā¦
Will apply it tomorrow if there wonāt be objections\better propositions.
List of files modified\added by patch:
client/CMT.cpp | 7 +
client/CMakeLists.txt | 2 +-
osx-vcmibuilder/innoextract | Bin 0 -> 2407224 bytes
osx-vcmibuilder/unshield | Bin 0 -> 56252 bytes
osx-vcmibuilder/vcmibuilder.icns | Bin 0 -> 1399181 bytes
.../vcmibuilder.xcodeproj/project.pbxproj | 307 ++++++++
osx-vcmibuilder/vcmibuilder/AppDelegate.h | 48 ++
osx-vcmibuilder/vcmibuilder/AppDelegate.m | 310 ++++++++
.../vcmibuilder/en.lproj/InfoPlist.strings | 2 +
osx-vcmibuilder/vcmibuilder/en.lproj/MainMenu.xib | 772 ++++++++++++++++++++
osx-vcmibuilder/vcmibuilder/main.m | 6 +
osx-vcmibuilder/vcmibuilder/vcmibuilder-Info.plist | 34 +
osx-vcmibuilder/vcmibuilder/vcmibuilder-Prefix.pch | 7 +Another small patch for OS X: dl.dropbox.com/u/1777581/vcmi/s ā¦ _fix.patch
Install and Compile OS X manuals for wiki are coming soon!
It seems that I will eventually need more OS X specific files than just osx-vcmibuilder dir.
Taking this into account what about organizing all packaging folders like debian, rpm and osx into some packaging folder instead of placing everything on root level?
For debian name of directory is more-less hardcoded (usually added during uploading to Debian repositories). Canāt say for rpm though.
Keeping one āosxā directory in root with all OS X-specific files in it sound fine for me.
Yes. Note that in most cases package maintainer is not a part of development team so this directory is stored separately as a āpatchā.
This is not true for VCMI so storing it directly in trunk is easier.
Now I get it. In such case just upload xcode-pack.zip please. So I could insert working link into OS X Building wiki page.
Yet another OS X compatibility patch: dl.dropbox.com/u/1777581/vcmi/a ā¦ atch.patch
Please provide xcode-pack.zip link once it is uploaded.
Finally Iām back. Can someone give me wiki access so I can start adding āHow to build VCMI (OS X)ā article?
You can login with your forum account.
Just wanted to say thank you to stopiccot for all the work heās done with the OS Xbuild. Setting up the workspace was a breeze thanks to him. Now I am starting to hunt bugs.
Hosting provided by DigitalOcean