On Thu, Dec 10, 2015 at 4:38 AM, Ruslan Baratov
wrote:
> This makes writing ExternalProject_Add steps with modification of
> environment quite non-trivial task (at least doing it correctly). This
> feature definitely missing in CMake. I've mentioned it once already:
> https://cmake.org/pipermail/c
On Wed, Dec 9, 2015 at 9:52 PM, Attila Krasznahorkay
wrote:
> Probably not the intended solution, but what I’m doing in such cases is that
> in a patch step I create a shell script that does the configuration for me.
> With all the environment settings and everything. Like:
>
> PATCH_COMMAND ${C
Hi Ruslan,
Thanks, this is good to know.
I absolutely agree that one needs to avoid using "&&" in the commands
themselves. As it also causes problems when you try to use
CTEST_USE_LAUNCHERS=1. (I myself ran into that issue...)
But I did not have any issues so far with putting "whatever" into a
On 10-Dec-15 12:52, Attila Krasznahorkay wrote:
Hi QP,
Probably not the intended solution, but what I’m doing in such cases is that in
a patch step I create a shell script that does the configuration for me. With
all the environment settings and everything. Like:
PATCH_COMMAND ${CMAKE_COMMAND
Hi QP,
Probably not the intended solution, but what I’m doing in such cases is that in
a patch step I create a shell script that does the configuration for me. With
all the environment settings and everything. Like:
PATCH_COMMAND ${CMAKE_COMMAND} -E echo “cd someDir/; CC=\”something\”
./config
Hi all,
I am trying to setup an ExternalProject in cmake but got stuck in the
configuration step. I am using ccache to speed up the compilation:
```
ExternalProject_Add(
...
CONFIGURE_COMMAND CC="ccache arm-linux-gnueabihf-gcc" ./configure
...
)
```
However, when cmake generates the Makefi
