<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 9, 2019 at 5:35 AM hex <<a href="mailto:hex7c3@gmail.com">hex7c3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
hello CMake community,<br>
<div class="gmail-m_7999541161878854554moz-forward-container"><br>
<br>
I am experimenting with external projects. I have some files in an
external project which are generated in `${CMAKE_SOURCE_DIR}`.<br>
<br>
<br>
When I add the external project, however, it is using
`${CMAKE_SOURCE_DIR}` of the external project.<br>
<br>
<br>
I need `${CMAKE_SOURCE_DIR}` to be relative to the "super build",
instead of the external project path.<br>
<br>
<br>
Example:<br>
<br>
<i>message("${CMAKE_SOURCE_DIR} = /home/user/super")</i><i><br>
</i><i><br>
</i><i>ExternalProject_Add(ext1</i><i><br>
</i><i> # directory options</i><i><br>
</i><i> SOURCE_DIR "${CMAKE_SOURCE_DIR}/ext1"</i><i><br>
</i><i>)</i><br>
<br>
<br>
${CMAKE_SOURCE_DIR}/ext1/CMakeLists.txt:<br>
<br>
<br>
<i>message("${CMAKE_SOURCE_DIR} = /home/user/super/ext1")</i></div></div></blockquote><div> </div><div><i>message("${CMAKE_SOURCE_DIR}/.. = /home/user/super/ext1/..")</i> which == /home/user/super</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_7999541161878854554moz-forward-container"><br>
<br>
<br>
The desired outcome would be to have the path /home/user/super in
both messages. </div>
<div class="gmail-m_7999541161878854554moz-forward-container">How can I do this?</div>
<div class="gmail-m_7999541161878854554moz-forward-container"><br>
</div>
<div class="gmail-m_7999541161878854554moz-forward-container"><br>
</div>
<div class="gmail-m_7999541161878854554moz-forward-container">thank you<br>
</div>
</div>
-- <br>
<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" rel="noreferrer" 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" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="https://cmake.org/mailman/listinfo/cmake" rel="noreferrer" target="_blank">https://cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div></div>