Available scripts:
- SuperInclude
- Win32 Application Cross-Compilation
- CMakeJar
All the scripts are found in this folder. Examples of usage can be found in the corresponding subfolders.
Provides github_include
macro that works like include
but it downloads
the macro from github if it's not present in the local file system.
Just include SuperInclude.cmake
and call the macro (see the
example).
You can find the available macros in SuperInclude.cmake.
This script is split in a functional basis. They can be used together or individually:
-
Win32CC.cmake
: main script. In order to use it, include it in your CMake script:set ( CMAKE_MODULE_PATH <location of Win32CC script if no default location> ) include ( Win32CC )
Find in Win32CC.cmake the available macros. The macros set some variables that help at cross-compiling and cross-testing (i.e. testing Windows binaries in a POSIX system).
-
Windows-mingw-i686.cmake
: toolchain file. This is the minimum CMake configuration needed if you wanted to compile for Windows. To use it call cmake as follows:cmake -DCMAKE_TOOLCHAIN_FILE=<path to Windows-mingw-i686.cmake> <path to the folder containing CMakeLists.txt>
In principle, you don't need to provide any other config file or variable, it will detect your configuration if your distribution is supported. For the time being, the supported distributions are: Fedora 15.
-
FindWine.cmake
: used byWin32CC.cmake
to check if Wine is present. If it is, WINE_FOUND and WINE_CMD are set accordingly.You can find an example here.
Provides a mean of loading files from Maven repository files. This can be useful when you need to use a dependency released in a Maven repository in your CMake project (e.g. a XML configuration file,...). It also contains a macro to unjar a jar.
Just include jar.cmake and call the macros found there (see the example).
Note: parse_arguments.cmake is needed by jar.cmake. I didn't write it.