On 3/27/13 10:49 AM, Andrey Tovchigrechko wrote: > At first, the configure stage failed because your latest commit still > contained a symlink.
Which symlink didn't it like?
> There were still a few errors with some Windows API functions > complaining about path format.
I don't get any of these - can you give an example?
> There was a lot of errors about various symbols present twice in the > same Boost library (program_options).
We link Boost explicitly. But at least on some Windows setups Boost does autolinking, so you might end up with it trying to link things twice. Defining BOOST_ALL_NO_LIB should fix that.
> There was a great number of warnings about symbols not being > exported. I guess they can be ignored?
I don't get any of those either - can you give an example?
> It also replaces a symlink inside scons directory with a Python > package that behaves like a symlink when imported.
That shouldn't be necessary, since that's only used by the scons build, and you're presumably using cmake here.
Ben