> On 22 Jul 2015, at 11:54, Uli Kusterer <witness.of.teacht...@gmx.net> wrote: > > On 22 Jul 2015, at 11:58, Dave <d...@looktowindward.com> wrote: >> Success! Thanks so much for your help Jonathan, I definitely owe you a pint >> or two! >> >> If anyone is trying use Dubrovnik/Mono on Mac OS X and needs to know how to >> make it work - give me a shout and I’d be happy to lend a hand. It’s >> probably better to mail me directly as it’s a little bit OT for this list. >> >> Thanks to everyone that contributed. > > > Could you maybe post the question and answer somewhere and do a quick > follow-up here with a link? It's always infuriating to find sth. via search > that says "I've solved it" and nothing more. In short:
1. Dubrovnik requires a 64 bit Mono build in order to make use of ARC. At present there is no 64 bit binary download and a Mono 64 build results in folder of framework components (which you may or may not be able to link to - not sure) but not an actual framework bundle. Dubrovnik has some instructions on how to cobble together a working framework but there is a bit of tinkering. There is a separate build tool call bockbuild but it is pretty opaque. Xamarin have a year end timeline for a supported 64 bit - and hopefully a working build workflow too. 2. The Dubrovnik repo as is has an issue with its one and only submodule. The submodule is not being correctly retrieved when pulling the initial repo. This needs sorted. Personally I often find that I have a working repo with submodules that looks hunky-dory but which, when initially pulled, has issues. Submodules are very useful but cause pain. I should be able to sort this fairly easily. 3. The mscorlib target is a work in progress and does not yet quite build successfully. I need to point this out in the docs. 4. The GUI sample app has a link issue. Again this is something that tends to appear when the repo is newly pulled. 2 targets generate frameworks and those frameworks are linked to by and embedded into the sample app. Linkage fails as the frameworks, though built cannot be found. The solution is to ensure that the framework location (as set in the inspector) is relative to the build folder not a realtive group path or so such. Again this is a straightforward fix. 5. The unit tests could not be run as I recalled previously running them. Perhaps this is due to a change in Xcode. Instead of running the tests from the Project navigator via menu Product - Test I had to use the Test navigator. The tests passed okay. It seemed to be then that after that initial test I could use menu Product - Test test to run the tests. A bit confusing. Jonathan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
