[CMake] copying files

Is there a simple cmake procedure to copy files from a source dir to the installation dir? thanks, Randy ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messag

[CMake] installing/overwriting single file

During an 'install', I would like to copy/overwrite a source file to a destination file. How? Something like the following (in syntax), although I am assuming that it is only legal to copy a file into a dir (and therefore the 'foo.cxx' isn't allow)? INSTALL(FILES ${CMA

Re: [CMake] installing/overwriting single file

ander Neundorf wrote: On Wednesday 04 November 2009, Randy Heiland wrote: During an 'install', I would like to copy/overwrite a source file to a destination file. How? Something like the following (in syntax), although I am assuming that it is only legal to copy a file into a dir

[CMake] Visual Studio 2017

Hello, I've googled "site:cmake.org/pipermail/cmake visual studio 2017" looking for answers, but still confused, so thought I'd ask this list. Is there a "best way" to use cmake for VS17 (but same cakelists for Linux)? And by "best", I mean with minimal effort on users. To be more specific, on Win

Re: [CMake] FW: Visual Studio 2017

make_learn\cmake_learn-master\build> nmake Microsoft (R) Program Maintenance Utility Version 14.11.25508.2 ... builds most of the way OK ... ... (but currently get an error at the end, trying to build code in my 'cmake_learn' repo) -Randy On Mon, Sep 18, 2017 at 10:22 PM, Randy Heiland

Re: [CMake] FW: Visual Studio 2017

at you're describing would not require a user having to fiddle with their PATH env var. On Tue, Sep 19, 2017 at 2:47 PM, Hendrik Sattler wrote: > > > Am 19. September 2017 17:51:31 MESZ schrieb Randy Heiland < > randy.heil...@gmail.com>: > >I failed to send my previ

Re: [CMake] FW: Visual Studio 2017

19. September 2017 22:05:36 MESZ schrieb Randy Heiland < > randy.heil...@gmail.com>: > >I'd love to learn more about this option, assuming it's a simple > >workflow > >via the command line. If there's a writeup related to cmake, would > >welcome

[CMake] cmake buried in subdirectory?

Hello, Simple question... can I/how can I keep my top-level cmake-related stuff in a subdirectory of my main project directory? E.g.: /myproj /cmake CMakeLists.txt and then in the /cmake, I create a /build from which I attempt: cmake .. I tried something as simple as this in my CMakeList

Re: [CMake] cmake buried in subdirectory?

component(SourceRoot "${CMAKE_CURRENT_SOURCE_DIR}/../../" > ABSOLUTE) > > The normal structure of the CMake file doesn't change, nothing special has > to be done with the project macro. Unless you have a more specific error, > that's about all the advice I have.

[CMake] simple find_package example

Hi, I'd like to figure out how to modify the simple "hello" demo ( https://cmake.org/examples/) so that the Hello project is a library with an accompanying FindHello.cmake and then the Demo project uses that information and "find_package" to discover/use it. Hopefully that makes sense. Basically,

Re: [CMake] simple find_package example

's some sort of "Find" template for any such lib, i.e., a project needs to be able to locate a lib (static or dynamic) and headers, cross-platform. thanks, Randy On Mon, Aug 6, 2018 at 4:09 PM, Alexander Neundorf wrote: > On 2018 M08 2, Thu 10:01:39 CEST Randy Heiland wrote: >