I ended up using a different approach based on ExternalProject:
include(ExternalProject)
ExternalProject_Add(c68kinc
DOWNLOAD_COMMAND ""
SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/c68k
CONFIGURE_COMMAND cmake
INSTALL_COMMAND ""
BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}/c68k
)
Settin
Guillaume Duhamel wrote:
> file(MAKE_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/c68k)
> execute_process(COMMAND cmake ${CMAKE_CURRENT_SOURCE_DIR}/c68k
> WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/c68k)
> add_custom_target(c68kinc COMMAND cmake --build
> ${CMAKE_CURRENT_BINARY_DIR}/c68k)
>
> It d
> (3)
> Use execute_process() to run the CMake command line tool and configure the
> host-only project during the configuration step of the main project. This
> will make the results of the export() command from the subproject available
> for loading by the main project. Then add a custom target
Michael Wild wrote:
> On 26. Jan, 2010, at 21:28 , Guillaume Duhamel wrote:
>> On the other hand, I've found out about the ExternalProject module in the
>> CMake documentation, could it be used to create a native-only CMake
>> sub-project?
Yes.
>> What I would really like is some way to have all
On 26. Jan, 2010, at 21:28 , Guillaume Duhamel wrote:
> Hi,
>
> I'm one of the Yabause ( http://yabause.org ) developers and we're currently
> porting our build system from Autotools to CMake. We made it to the point
> were basic stuff is working and we now want to get cross compilation working
Hi,
I'm one of the Yabause ( http://yabause.org ) developers and we're currently
porting our build system from Autotools to CMake. We made it to the point
were basic stuff is working and we now want to get cross compilation working
too.
One of Yabause compilation step require to generate and run
