[CMake] actually using cmake alternative to convenience libraries

[Tamás Kenéz]

> set(foobarSRCS foo.c bar.c)
> set(foobarLIBS ${externalLibFound})
>
> which is what the FAQ entry seems to suggest. However, this variable is
not visible to goo.c. Okay, so as an alternative, I can do this:
>
> set(foobarSRCS foo.c bar.c PARENT_SCOPE), etc.

In similar cases I create CACHE variables:

    set(foobarSRCS foo.c bar.c CACHE INTERNAL "" FORCE)
    set(foobarLIBS ${externalLibFound} CACHE INTERNAL "" FORCE)

You can also write a set_cache() macro.

Tamas

On Tue, Nov 17, 2015 at 4:37 PM, Jack Stalnaker <jack.stalnaker at gmail.com>
wrote:

> I'm trying to figure out the best way to handle something that was a
> convenience lib under autotools. I realize that there's a FAQ entry here:
>
>
> https://cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_libraries.3F
>
> But its terse 2 paragraphs don't say how to actually do what it suggests.
> My problem is this. I have this source tree:
>
> lib
> |--foo.c
> |--foo.h
> |--bar.c
> |--bar.h
> |--baz.c
> src
> |--goo.c
>
> In lib, I need to somehow collectively refer to foo and bar. Okay, so I
> can create a variable:
>
> set(foobarSRCS foo.c bar.c)
> set(foobarLIBS ${externalLibFound})
>
> which is what the FAQ entry seems to suggest. However, this variable is
> not visible to goo.c. Okay, so as an alternative, I can do this:
>
> set(foobarSRCS foo.c bar.c PARENT_SCOPE), etc.
>
> but now the variable is not visible to baz.c, which also must include the
> srcs to create a module library called _baz! I can of course do something
> like this:
>
> set(foobarSRCSLOC foo.c bar.c)
> set(foobarSRCS ${foobarSRCSLOC} PARENT_SCOPE)
>
> but this feels dirty and repetitive.
>
> I also realize that I can just create the variables in src, but that kind
> of defeats the entire purpose of walling of the common libs and their
> dependencies in the first place.
>
> Is this the right way to work, or am I missing something simple?
>
> --Jack
>
> --
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20151119/1793daa7/attachment.html>