Hi Pascal,

Thanks for the patches.

Can you share with us why setting CMAKE_FIND_ROOT_PATH does not work, or how 
this new method compares?

For example, in the toolchain file:
SET(CMAKE_FIND_ROOT_PATH  /path/to/Qt ...)

Clint

On Wednesday, July 29, 2015 02:32:48 PM Pascal Bach wrote:
> ---
>  Modules/FindQt4.cmake | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/Modules/FindQt4.cmake b/Modules/FindQt4.cmake
> index 9d03378..64c06e1 100644
> --- a/Modules/FindQt4.cmake
> +++ b/Modules/FindQt4.cmake
> @@ -29,6 +29,26 @@
>  #  for a particular executable, set the ``QT4_NO_LINK_QTMAIN`` target
>  #  property to ``TRUE`` on the executable.
>  #
> +# Cross Compile
> +# ^^^^^^^^^^^^^
> +#
> +# To find Qt in a cross compile environment set the following variables in
> your toolchain file: +#
> +#
> +# ``QT_BINARY_DIR``  => Path to native Qt binary directory
> +# ``QT_LIBRARY_DIR`` => Path to target Qt library directory
> +# ``QT_INCLUDE_DIR`` => Path to target Qt include directory
> +# ``QT_MKSPECS_DIR`` => Path to target Qt mkspecs directory
> +
> +# example
> +#
> +# ::
> +#   set( QT_BINARY_DIR   /sysroots/x86_64-linux/usr/bin )
> +#   set( QT_LIBRARY_DIR  /sysroots/arm/usr/lib )
> +#   set( QT_INCLUDE_DIR  /sysroots/arm/usr/include/qtopia )
> +#   set( QT_MKSPECS_DIR  /sysroots/arm/usr/share/qtopia/mkspecs )
> +#
> +#
>  # Qt Build Tools
>  # ^^^^^^^^^^^^^^
>  #

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to