Hi,
It seems that ADD_DEPENDENCIES does not allow to add a dependency to every
target. Here is a brief description of the problem:
A subdirectory contains a custom target to generate html from a docbook:
ADD_CUSTOM_TARGET(doc-test
COMMAND xmlto html
${CMAKE_CURRENT_SOURCE_DIR}/
Anyone having a simple example of CMake setup to support target named
say "docs" in CMake generated makefile so that "make docs" would
generate project documentation using Doxygen?
Thanks.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mail
ADD_CUSTOM_TARGET(doc COMMAND doxygen ${include_BINARY_DIR}/Doxyfile)
For instance...
2007/2/5, Crni Gorac <[EMAIL PROTECTED]>:
Anyone having a simple example of CMake setup to support target named
say "docs" in CMake generated makefile so that "make docs" would
generate project documentation
2007/2/5, Crni Gorac <[EMAIL PROTECTED]>:
Anyone having a simple example of CMake setup to support target named
say "docs" in CMake generated makefile so that "make docs" would
generate project documentation using Doxygen?
Here you go the following example add "apidoc" and "apidoc_forced" tar
On 2007-02-05 17:18+0100 Crni Gorac wrote:
Anyone having a simple example of CMake setup to support target named
say "docs" in CMake generated makefile so that "make docs" would
generate project documentation using Doxygen?
Yes.
Browse the subversion repository of libLASi project at
http://la
On 2007-02-05 15:58+0100 frederic heem wrote:
Hi,
It seems that ADD_DEPENDENCIES does not allow to add a dependency to every
target. Here is a brief description of the problem:
A subdirectory contains a custom target to generate html from a docbook:
ADD_CUSTOM_TARGET(doc-test
C
2007/2/5, Alan W. Irwin <[EMAIL PROTECTED]>:
On 2007-02-05 17:18+0100 Crni Gorac wrote:
> Anyone having a simple example of CMake setup to support target named
> say "docs" in CMake generated makefile so that "make docs" would
> generate project documentation using Doxygen?
Yes.
Browse the sub
I've implemented the ability to reference C# projects in a vc80 .sln
solution file with INCLUDE_EXTERNAL_MSPROJECT. Though, it is not a
small isolated code snippet. Here are the steps I took:
- I added cmGlobalVisualStudio71Generator::GetPlatform(), which
returns "Win 32", and is overridden in cm
I just checked a fix into CVS, that reads the GUID from an external
project and uses that instead of generating a new one. (caused an error
with VS 2005 SP1). You may want to update and start with that code.
The code uses an XML parser, so you should be able to figure out the
type of exter
On 2007-02-05 20:04+0100 Eric Noulard wrote:
2007/2/5, Alan W. Irwin <[EMAIL PROTECTED]>:
Browse the subversion repository of libLASi project at
http://lasi.svn.sourceforge.net/viewvc/lasi/trunk/.
[...]One nasty complication is the "INSTALL(DIRECTORY ..." pattern we use to
install the doxyge
10 matches
Mail list logo