<div dir="ltr">Hi Folks, <div><br></div><div>I would like to discussed the usable of "export(PACKAGE ...)" statement. </div><div><div style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></div>
<div style="font-family:arial,sans-serif;font-size:12.800000190734863px">Based on my experience, it turns out that exporting the build tree in the system package registry is a bad idea when building the same package multiple time as it is done on a dashboard client or a developer workstation trying out multiple configurations. Indeed, when "find_package" is used in "CONFIG" (or "NO_MODULE") mode, by default CMake will search into the CMAKE_SYSTEM_PACKAGE_REGISTRY and will resolve to an already generated build tree instead of the one passed using <PROJECT_NAME>_DIR.</div>
<div style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></div><div style="font-family:arial,sans-serif;font-size:12.800000190734863px">What do you think ? Should we deprecate the use of "export(PACKAGE ..)" or add a warning in the documentation ? </div>
<div style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></div><div style="font-family:arial,sans-serif;font-size:12.800000190734863px">Reference: <a href="http://www.cmake.org/cmake/help/v2.8.10/cmake.html#command:export" style="font-family:arial;font-size:small">http://www.cmake.org/cmake/help/v2.8.10/cmake.html#command:export</a></div>
<div style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></div><div style="font-family:arial,sans-serif;font-size:12.800000190734863px">Thanks</div><div style="font-family:arial,sans-serif;font-size:12.800000190734863px">
Jc</div><div><br></div>-- <br>+1 919 869 8849<br>
</div></div>