<div dir="ltr">Hi Magnus.<br><br>I am afraid that's not really possible (safely). CMake uses absolute paths all over the place (by design), so all output file paths etc. are hardcoded in the .sln and .vc[x]proj files to the paths applicable where they were generated. You can experiment with the variable CMAKE_USE_RELATIVE_PATHS, but even its documentation warns that it's unreliable.<br>
<br>Petr<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 10:23 AM, Magnus Therning <span dir="ltr"><<a href="mailto:magnus@therning.org" target="_blank">magnus@therning.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi CMake list,<br>
<br>
A colleague and I are trying to somewhat sneak in CMake in a project<br>
that uses Visual Studio for IDE. This is a fairly big step to take<br>
and we anticipate a bit of push-back, even if it clearly is a<br>
worthwhile improvement. One way to maybe ease the transition would be<br>
to check in the CMake-generated solution+projects. I took the naive<br>
approach and just removed the CMake-generated files, the cache etc,<br>
just keeping the VS solution+projects. The next build I noticed that<br>
CMake was re-run and the cache was regenerated.<br>
<br>
Is there some way to get CMake to generate solution+projects that<br>
don't have any tie to CMake at all, its cache or CMakeLists.txt files,<br>
that are suitable to check into a VCS and thereby not require every<br>
user of the code to install CMake themselves?<br>
<br>
I am well aware of the potential problems arising from CMake not being<br>
a round-trip tool, i.e. that changes made to the solution+projects<br>
don't end up in the CMakeLists.txt automatically. At this point in<br>
time that isn't a big concern for us though.<br>
<br>
/M<br>
<br>
--<br>
Magnus Therning OpenPGP: 0xAB4DFBA4<br>
email: <a href="mailto:magnus@therning.org">magnus@therning.org</a> jabber: <a href="mailto:magnus@therning.org">magnus@therning.org</a><br>
twitter: magthe <a href="http://therning.org/magnus" target="_blank">http://therning.org/magnus</a><br>
--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake community. For more information on each offering, please visit:<br>
<br>
CMake Support: <a href="http://cmake.org/cmake/help/support.html" target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" target="_blank">http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br></div>