Hi Alan,
On Fri, Mar 7, 2014 at 6:35 AM, Alan W. Irwin wrote:
>
> To solve the issue you have described, I suggest you create a simple
> overall project that configures the build of _both_ your principal
> project and the project it depends on using the ExternalProject_Add
> command.
I guess thi
On 2014-03-06 21:47+0100 Alejandro Martinez Ruiz wrote:
Hi list,
I have a problem trying to properly install my project with CMake.
My project has a dependency on an external project, which I
conveniently download, build and install using the ExternalProject
module. What I have at this point i
Hi list,
I have a problem trying to properly install my project with CMake.
My project has a dependency on an external project, which I
conveniently download, build and install using the ExternalProject
module. What I have at this point is the following:
1) This external project produces a set o
Hm ok, found it by myself
I'm trying to install some generated files (example):
CMAKE_MINIMUM_REQUIRED(VERSION 2.4)
SET(XFILE foo.x)
SET(ZFILE foo.z)
SET_SOURCE_FILES_PROPERTIES(${ZFILE} PROPERTIES GENERATED TRUE)
ADD_CUSTOM_COMMAND(OUTPUT ${ZFILE}
COMMAND cp
ARGS ${XFILE} ${ZFILE}
DEPENDS $
Hi!
I'm trying to install some generated files (example):
CMAKE_MINIMUM_REQUIRED(VERSION 2.4)
SET(XFILE foo.x)
SET(ZFILE foo.z)
SET_SOURCE_FILES_PROPERTIES(${ZFILE} PROPERTIES GENERATED TRUE)
ADD_CUSTOM_COMMAND(OUTPUT ${ZFILE}
COMMAND cp
ARGS ${XFILE} ${ZFILE}
DEPENDS ${XFILE}
WORKING_D
On Nov 28, 2007 6:45 AM, Stefan Kögl <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 28. November 2007 10:38:20 schrieb Brandon Van Every:
> > You need to know the names of the files that will be generated and
> > then INSTALL(FILES ...)
> > Typically I just have a hardwired list of root words, from whic
I would think:
INSTALL(DIRECTORY )
would do it in one command without knowledge of the sub-structure of the
directory.
Is there something wrong with that approach?
It should be less error prone than gathering knowledge of doxygen output
just for specifying a bunch of install rules that essen
Am Mittwoch, 28. November 2007 10:38:20 schrieb Brandon Van Every:
> You need to know the names of the files that will be generated and
> then INSTALL(FILES ...)
> Typically I just have a hardwired list of root words, from which I
> derive .cxx .hxx and whatever a doxygen suffix is. Here are some
You need to know the names of the files that will be generated and
then INSTALL(FILES ...)
Typically I just have a hardwired list of root words, from which I
derive .cxx .hxx and whatever a doxygen suffix is. Here are some
helper routines. You're probably also going to want an
ADD_CUSTOM_COMMAND
Hi,
how to install files generated by custom targets, eg. doxygen? The files are
generated in ${DOXYGEN_BINARY_DIR}/html ( /doc/html ).
here is the /doc/CMakeLists.txt
##
PROJECT(doxygen)
FIND_PACKAGE(Doxygen REQUIRED)
CONFIGURE_FILE(${doxygen_SOURC
10 matches
Mail list logo