2010/11/19 Thomas Lehmann
>
> Hi,
>
>
>
> I’ve found an example to use bison and flex in cmake.
>
> I have a static library where I want to add the generated
>
> sources but the dependencies are not triggered. Why?
>
>
>
> project(test)
>
>
>
> include_directories(.
>
> ${CMAKE
Hi,
I've found an example to use bison and flex in cmake.
I have a static library where I want to add the generated
sources but the dependencies are not triggered. Why?
project(test)
include_directories(.
${CMAKE_BINARY_DIR}/libs/test)
add_custom_target(ScannerAndParser echo
On 11/18/2010 10:59 PM, luxInteg wrote:
> Greetings
>
> I am learning cmake
> I downloaded CMakeUseLatex from
> http://www.cmake.org/Wiki/CMakeUserUseLATEX
>
> and I scanned through the pdf file but I did not see any references to TEX
> binaries such docbook2html, dblatex etc.
Those are N
On Thu, Nov 18, 2010 at 10:55:15PM -0500, Braden Walters wrote:
> #Install headers
> set(HEADERS
> test.hpp)
> foreach(HEADER ${HEADERS})
> install(TARGETS ${CMAKE_CURRENT_SOURCE_DIR}/include/${HEADER}
> DESTINATION ${CMAKE_INSTALL_PREFIX}/include/PROJECT/${HEADER})
> endforeach()
Try
Hi. I'm having some issues with the install() command in CMake. I have
the following code:
#Install headers
set(HEADERS
test.hpp)
foreach(HEADER ${HEADERS})
install(TARGETS ${CMAKE_CURRENT_SOURCE_DIR}/include/${HEADER}
DESTINATION ${CMAKE_INSTALL_PREFIX}/include/PROJECT/${HEADER})
BRL-CAD's experimental CMake build is using xsltproc and fop currently
rather than TEX binaries, but the techniques probably can be adapted to
other tools - you might want to take a look at:
http://brlcad.svn.sourceforge.net/viewvc/brlcad/brlcad/branches/cmake/doc/docbook/CMakeLists.txt?revision=4
On 11/18/2010 11:01 PM, Russell L. Carter wrote:
> Hi all,
> I have three g++ versions installed. Debian's native g++-4.3 and
> g++-4.4 both use /usr/lib/libstdc++.so.6.13, while
> /usr/local/bin/g++-4.5 needs /usr/local/lib64/libstdc++.so.6.14.
>
> If I use CXX=/usr/local/bin/g++-4.5 at configur
Hi,
I apologize of this is a trivial question but I cannot seem to find an answer
or get it to work. I am building an installation package for MacOS X using
package maker. I cannot figure out how to let the user override the
installation directory when they open the .mpkg file. Can anyone help?
Hi all,
I have three g++ versions installed. Debian's native g++-4.3 and
g++-4.4 both use /usr/lib/libstdc++.so.6.13, while
/usr/local/bin/g++-4.5 needs /usr/local/lib64/libstdc++.so.6.14.
If I use CXX=/usr/local/bin/g++-4.5 at configure time, executables
are linked against /usr/lib/libstdc++.so.
UseLATEX.cmake has no facilites for docbook. It was designed strictly with the
latex and pdflatex programs in mind.
-Ken
On 11/18/10 2:59 PM, "luxInteg" wrote:
Greetings
I am learning cmake
I downloaded CMakeUseLatex from
http://www.cmake.org/Wiki/CMakeUserUseLATEX
and I scanned through
Greetings
I am learning cmake
I downloaded CMakeUseLatex from
http://www.cmake.org/Wiki/CMakeUserUseLATEX
and I scanned through the pdf file but I did not see any references to TEX
binaries such docbook2html, dblatex etc. So lets say I have a couple a
docbook_xml files xyxy.docbook ab
On Wednesday 17 November 2010, luxInteg wrote:
> Greetings,
>
> I am learning cmake.
>
> I am looking for a tool to converta build system fom autoconf to
> cmake. II came across am2cmake available at
> http://websvn.kde.org/trunk/KDE/kdesdk/cmake/scripts/
>
> It is very kde3 specific, I was w
2010/11/18 David Cole :
> On Thu, Nov 18, 2010 at 1:08 PM, Denis Scherbakov
> wrote:
>> Here is a sample CMakeLists.txt to illustrate that two custom targets cannot
>> depend on each other:
>>
>> PROJECT(BUG C)
>>
>> CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
>>
>> ADD_CUSTOM_COMMAND(
>> OUTPUT "${CMA
On 2010-11-18 07:18-0800 Denis Scherbakov wrote:
David,
Thank you for spending your time to resolve my problem.
Unfortunately you suggestion did not help.
Introduction of new custom targets in my case leads to the fact that
I have one custom target that depends on another custom target. I get
On Thu, Nov 18, 2010 at 1:08 PM, Denis Scherbakov
wrote:
> Here is a sample CMakeLists.txt to illustrate that two custom targets cannot
> depend on each other:
>
> PROJECT(BUG C)
>
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
>
> ADD_CUSTOM_COMMAND(
> OUTPUT "${CMAKE_CURRENT_BINARY_DIR}/fileOne"
> CO
Here is a sample CMakeLists.txt to illustrate that two custom targets cannot
depend on each other:
PROJECT(BUG C)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
ADD_CUSTOM_COMMAND(
OUTPUT "${CMAKE_CURRENT_BINARY_DIR}/fileOne"
COMMAND "${CMAKE_COMMAND}"
ARGS "-E"
"touch"
"${CM
Hello,
I'm using CMake custom commands to copy files from a source directory to a
project binary one. The copying commands itself looks this way:
add_custom_command( OUTPUT "${dest_file}"
COMMAND "${CMAKE_COMMAND}" -E copy "${src_file}" "${dest_file}"
DEPENDS "${src_file}"
)
After all "add_cus
David,
Thank you for spending your time to resolve my problem.
Unfortunately you suggestion did not help.
Introduction of new custom targets in my case leads to the fact that
I have one custom target that depends on another custom target. I get:
gmake[3]: *** No rule to make target 'customTarge
Try:
ADD_CUSTOM_TARGET(MyHeaders ALL DEPENDS MyFile.hh)
Without the "ALL" your target is not included in the set of targets
built by a "make" or a "make all" -- without your target included in
"make" there is nothing for the subsequent targets to depend on.
Perhaps we should add a warning to add_d
Hi, David,
I did as you suggested:
ADD_CUSTOM_COMMAND(OUTPUT MyFile.hh ...)
ADD_CUTSOM_TARGET(MyHeaders DEPENDS MyFile.hh)
ADD_LIBRARY(MYLIB ${MYLIB_SRCS})
ADD_DEPENDENCIES(MYLIB MyHeaders)
ADD_LIBRARY(MYLIBpic ${MYLIB_SRCS})
ADD_DEPENDENCIES(MYLIBpic MyHeaders)
Didn't work. Target "MyHeader
When configuring ParaView (and other applications), I see this:
CTest cannot determine repository type. Please set UPDATE_TYPE to 'cvs' or
'svn'. CTest update will not work.
Is CTest aware of git?
Thanks,
David
___
Powered by www.kitware.com
Visit ot
Hi, Marcel,
What I mean is that I have a huge source tree and many CMake files and there is
a source file inside this tree that needs to be built two times, because there
will be an executable using it (non-PIC) and a shared library (PIC). So I have
to create two targets (say MYLIB and MYLIBpic
On Thu, Nov 18, 2010 at 8:34 AM, Denis Scherbakov
wrote:
> Hi!
>
> What I mean is:
>
> PROJECT(MYPROJECT)
>
> ADD_CUSTOM_COMMAND( OUTPUT "${PROJECT_BINARY_DIR}/MyFile.hh" COMMAND
> ${CMAKE_COMMAND} -P MyScript.cmake)
>
> SET_SOURCE_FILE_PROPERTIES("${PROJECT_BINARY_DIR}/MyFile.hh" PROPERTIES
> G
Hi!
What I mean is:
PROJECT(MYPROJECT)
ADD_CUSTOM_COMMAND( OUTPUT "${PROJECT_BINARY_DIR}/MyFile.hh" COMMAND
${CMAKE_COMMAND} -P MyScript.cmake)
SET_SOURCE_FILE_PROPERTIES("${PROJECT_BINARY_DIR}/MyFile.hh" PROPERTIES
GENERATED TRUE HEADER_FILE_ONLY TRUE)
SET (MYPROJECT_SRCS
MyFile.hh
MyFi
2010/11/18 Denis Scherbakov :
> Dear All,
>
> I am using CMake 2.8.1 on Linux x86. I have a project that needs to be built
> two times. One with -fPIC, the other - without. The project depends on header
> files that need to be generated by an external script.
>
> When I build this project with se
>>> On 18-11-2010 at 13:06, in message
<306960.51089...@web65407.mail.ac4.yahoo.com>, Denis Scherbakov
wrote:
> Dear All,
>
> I am using CMake 2.8.1 on Linux x86. I have a project that needs to
be built
> two times. One with -fPIC, the other - without. The project depends
on header
> files tha
Dear All,
I am using CMake 2.8.1 on Linux x86. I have a project that needs to be built
two times. One with -fPIC, the other - without. The project depends on header
files that need to be generated by an external script.
When I build this project with several parallel jobs (gmake -j5, for exampl
On Wed, 17 Nov 2010 13:12:42 +0100
Yngve Inntjore Levinsen wrote:
> On Wednesday 17 November 2010 12:30:06 Adam J Richardson wrote:
> > Is this a correct specification for multiple include/lib paths in
> > environment variables? If not, what should I use instead? Sometimes
> > it seems to work, o
28 matches
Mail list logo
