Hi Peter,
as I don't use windows at all, this is just a very wild guess...
Could it be that in the second run you actually don't use
/CMake/share/cmake-3.2/Modules/FindBoost.cmake
but boost-config.cmake, which it now finds in the cached environment of
the first run?
This assumes of course
up with would be patching
cmMakefile.cxx. Before I go on asking for a feature addition to
cmake, I'd like to know whether I can solve my problem by other means.
Any ideas?
Benedikt
On Nov 24, 2010, at 12:17 PM, Benedikt Hegner wrote:
Hello,
I am facing a problem here on conflicts
Hello,
I am facing a problem here on conflicts between imported targets and
custom targets. Basically I want to override an imported target by a
custom target of the same name. A solution like avoiding clashes
using NAMESPACE on EXPORT doesn't really work for me as the identical
naming