Hi,
I have implemented a scheduler with Gecodej 2.1.1 using Eclipse under WinXP.
The main scope can be summarized as:
for(int i=0, iI noticed that for i=3 I get some suboptimal solutions but the B&B
cannot be completed and the program exits with an error. I have
attached the correspondent lo
Hi,
First of all, you should really use the new version, Gecode 2.2.0 has
several important bug-fixes.
Secondly, I'm not sure if you are experiencing troubles with
memory-consumption, since the error-log indicates that you have around
90 Mb of free memory. Unfortunately I have no direct ideas as
[EMAIL PROTECTED] wrote:
> I have implemented a scheduler with Gecodej 2.1.1 using Eclipse
> under WinXP.
> The main scope can be summarized as:
>
> for(int i=0, i
> scheduler.loadBenchmark(i);
> scheduler.solveBenchmark(i);
> scheduler.printResult();
> }
>
> I am using a BranchAndBound str
Hi everyone!
We had a bit of trouble trying to link to the binary Gecode
distribution from a Microsoft Visual Studio C++ project. First of
all, here's what you have to set up in the properties dialog of your
"Solution":
* Configuration Properties, C++, General, set the Additional Include
As a slight addition: first, our thanks to Jan Kelbel, for helping us to
reproduce and analyze the bug.
Then, in 3.0 Gecode will use auto-linking with MSVC: so it is sufficient to
give the library directory. The respective libraries will be found
automatically by the linker.
Christian
--
Christi
Hi,
> We had a bit of trouble trying to link to the binary Gecode
> distribution from a Microsoft Visual Studio C++ project. First of
> all, here's what you have to set up in the properties dialog of your
> "Solution":
> * Configuration Properties, C++, General, set the Additional Include
Hi,
as an example just try one of the Gecode examples! We have digged deeper and
know a little bit more: mixing DLLs created with -MD (as we do) with other
stuff created with -MDd for debugging gets you into trouble.
The trouble can be observed when using std::ostream... (try printing a
variable)
Oh, two more things: it is not an issue with different versions of MSVC, we
used the same version. And most importantly, after some thinking it is quite
clear why it should not work: you link std::ostream twice, once inside the
Gecode DLLs against the optimized MSVC libs, and the second time in you
