make.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:
> https://cmake.org/mail
Hi Chris,
Is “tbb” used as a target name and direct link anywhere? e.g.
add_library(tbb IMPORTED …)
then somewhere else
target_link_libraries(foo PUBLIC tbb)
(you mentioned use of a config Cmake file)? One thing that bit me a while ago
(but I don’t think
it’s a CMake bug per se) is that if
sulting: 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://publ
not sure if I've misunderstood how
CMAKE_CXX11_{STANDARD,EXTENSION}_COMPILE_OPTION is supposed to work, or if
there's some other setting I'm missing. Any help or suggestions gratefully
received!!
Thanks,
Ben Morgan
--
Powered by www.kitware.com
Please keep messages on-topic and
Hi Mojca,
On 27 June 2014 10:26, Mojca Miklavec wrote:
> On Fri, Jun 27, 2014 at 10:42 AM, Angeliki Chrysochou wrote:
> > Hi Mojca,
> >
> > From what I know cmake will look for libraries in the directories
> specified
> > in link_directories(${LIBRARY_DIRS}) and for headers in the directories
>
Hi Eli,
On 21 June 2012 21:25, Ateljevich, Eli wrote:
> Hi,
>
> I was wondering if there is a best practice for providing a file for user
> configuration decisions (options, unique flags) that will be more
> persistent than the cache? I have a project where a dozen or two
> algorithmic decis
Hi Michael,
On Thu, May 5, 2011 at 10:48 PM, Michael Hertling wrote:
>
> IMO, your approach looks quite reasonable; however, I'm not completely
> happy with it... ;) Please note that the following remarks are just my
> personal point of view, and of course, one can have different notions.
>
> The
Hi,
I've been working on adding Config.cmake support to my CMake based
projects, and just had a quick question regarding 'best practice' in writing
these when the project builds both dynamic and (optionally) static
libraries, with clients of the project wishing to choose one or the other.
Thanks
lution overall since everything would be
under the CMake umbrella?
Best Regards,
Ben Morgan.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic