Hi Andrey.

As a workaround, you could make the calling context a macro instead of a
function. Macros don't introduce variable scope.

Petr

On Fri, Nov 7, 2014 at 4:23 PM, Andrey Upadyshev <oli...@gmail.com> wrote:

> Hello!
>
> I'm writing a wrapper around find_package so I call find_package from my
> own function. I found it's near impossible because all the variables set by
> finders remain in the scope of my wrapper function, rather than in the
> caller's scope. Is there any way to force find_package to set all variables
> in my function caller's scope? I.e. something like find_package(...
> PARENT_SCOPE)?
>
> Thank you,
> Andrey
>
> --
>
> 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
>
-- 

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

Reply via email to