Alexander Neundorf <[EMAIL PROTECTED]>
writes:
>> >> The problem is in execute_process. The cmake process created by it is
>> >> taking variable values from the enclosing cmake, so it uses the same
>> >> compiler, configure variables, etc.
>> >
>> > What do you mean by "variables"?
>> > CMake one
On Monday 10 November 2008, Óscar Fuentes wrote:
> Eric NOULARD <[EMAIL PROTECTED]>
>
> writes:
> >> The problem is in execute_process. The cmake process created by it is
> >> taking variable values from the enclosing cmake, so it uses the same
> >> compiler, configure variables, etc.
> >
> > What
Eric NOULARD <[EMAIL PROTECTED]>
writes:
>> The problem is in execute_process. The cmake process created by it is
>> taking variable values from the enclosing cmake, so it uses the same
>> compiler, configure variables, etc.
>
> What do you mean by "variables"?
> CMake one or
> Environment one?
Le Sun, 09 Nov 2008 22:24:45 +0100,
Óscar Fuentes <[EMAIL PROTECTED]> a écrit :
> While cross-compiling, I'm trying to avoid depending on previously
> built executables, that is, the cross-compile build should create the
> native utilities it needs. For this, I'm trying
>
> execute_process(
> CO
While cross-compiling, I'm trying to avoid depending on previously built
executables, that is, the cross-compile build should create the native
utilities it needs. For this, I'm trying
execute_process(
COMMAND ${CMAKE_COMMAND} -DCMAKE_BUILD_TYPE=Release ${CMAKE_SOURCE_DIR}
WORKING_DIRECTORY ${CX
