[gecode-users] embedded gecode

[Ruben Zilibowitz]

On 05/04/2011, at 5:18 PM, Guido Tack wrote:

> Ruben Zilibowitz wrote:
> 
>> Thanks for the tip about setting the commit and adaptive distance. That helps memory wise. In order to compile gecode for iphone one needs to set "Compile for Thumb" to "No", in case anyone else wants to try. There are two more issues I'm having.
>> 
>> 1) Is gecode thread safe, in general? In particular can I safely initialise a space and run a search on it all inside of a thread? This is important since one doesn't want to block execution in an iphone app.
> 
> Yes, no problem at all.  You just can't call methods on the same space from two different threads concurrently.

Ok. Great.

> 
>> 2) My executables, even after dead code elimination and other optimisations are very large. It's around 17 Mb. I'm not sure there's an easy fix for this, but any ideas would be welcome, for how to reduce file size of the executable. It seems that there are many features I'm not going to need, so perhaps I can try to strip down the library.
> 
> First of all, that sounds like you're linking statically, right?  It's true, the Gecode libraries are a bit on the fat side.  What you can definitely do is strip the debug symbols.  Other than that, I think the linker already only includes the symbols that it needs, so there's not much you can do in addition.

Yes, statically. I'm not sure there's any other way when it comes to building iPhone apps. That 17 Mb is for a "fat" binary that supports two architectures (armv6 and armv7). So the real figure is about half that. Still it would be nice to try and cut it down somewhat.

Ruben