Hi Matthaus,
do you need the pre-configure step to happen at build time? Would it be an
option for you to use file(WRITE) instead of configure_file(), and
execute_process() instead of add_custom_target()? Basically, perform the
pre-configure step as part of the first CMake run itself.
What if you call your dependency-fetcher script with a straight
macro/function call or `include` or `execute_process` instead of putting it
into a custom target? I'm thinking of something like this:
set(DEP_SCRIPT_OUT ${CMAKE_CURRENT_BINARY_DIR}/dep-script-out.cmake)
if(NOT EXISTS
On 9/24/2015 4:26 PM, Matthäus G. Chajdas wrote:
Hi,
that sounds like it would do the trick. I wasn't aware that
execute_process will block the script until it's done executing. Need to
check this out but that definitely looks like the way to go, thanks!
ExternalProject might be a better
On 9/24/2015 5:02 PM, Matthäus G. Chajdas wrote:
Hi,
how does the ExternalProject interact with subsequent find_library calls?
I've seen projects building dependencies through ExternalProject, but
those would the project manually by querying ExternalProject and adding
a new imported target.
Hi,
that sounds like it would do the trick. I wasn't aware that
execute_process will block the script until it's done executing. Need to
check this out but that definitely looks like the way to go, thanks!
Cheers,
Matthäus
Am 24.09.2015 um 10:14 schrieb Tamás Kenéz:
> What if you call your
Hi,
how does the ExternalProject interact with subsequent find_library calls?
I've seen projects building dependencies through ExternalProject, but
those would the project manually by querying ExternalProject and adding
a new imported target. How would I connect an ExternalProject to one or
more
Hi,
I'm trying to solve the following the problem: I have a C++ application
and a dependency fetching script. I want to simplify the initial build
such that the following happens: On the first run of cmake, the compiler
ID and version is passed to an external script, which fetches some
pre-build
