Well, I don't really understand your model. What's an incrementation?
The only way I can imagine how you want your model to work is to just
split the element constraint in two. I.e., have two arrays a0 and a1
of integers (or IntVars), such that is the edge i, and
then use element(a0,b,d0
Hi all,
I've tried (and failed) to compile and linked Gecode statically.
./configure --enable-static doesn't seem to change anything and if I add -static
manually, it fails to compile with
g++ -pthread -static gecode/support/exception.o gecode/support/heap.o
gecode/support/thread/thread.o gecod
Hi Lars,
we currently don't support creating both static and dynamic libraries,
and our configure script has a bug, it doesn't switch off dynamic libs
when you say --enable-static. Please try --enable-static --disable-
dynamic, I think it should work.
Cheers,
Guido
Lars Kotthoff wr
> we currently don't support creating both static and dynamic libraries,
> and our configure script has a bug, it doesn't switch off dynamic libs
> when you say --enable-static. Please try --enable-static --disable-
> dynamic, I think it should work.
Thanks Guido, unfortunately it still does
The Gecode libs themselves cannot be linked statically (e.g. against
libstdc++), they're just archives of object files, after all. One
problem with the current build system is that if you've built dynamic
libs before and they're still in the directory, they will be used for
linking. If yo
> One problem with the current build system is that if you've built dynamic
> libs before and they're still in the directory, they will be used for
> linking. If you --enable-static --disable-dynamic in a fresh source
> directory, the executables should be linked against the static Gecode libs.
Lars Kotthoff wrote:
> ./configure --enable-static --disable-dynamic && make
> in a clean source directory builds the static and dynamic libs (by
> which I mean
> the .a and .so files) and links the example binaries dynamically, e.g.
Ah, sorry, it's called --disable-shared, not --disable-dynamic
> I played with this a bit, and the problem with -static is that it only
> works if all libraries are actually available as static libraries,
> which sometimes they aren't (e.g. on a Mac).
On Mac (and probably Windows) it's quite reasonable not to link completely
statically I think because the
