Thanks Eric, please see following embedded comments.
On Thu, Jun 21, 2012 at 10:32 PM, Eric Noulard eric.noul...@gmail.comwrote:
2012/6/21 hce jupiter@gmail.com:
Hi,
There were some discussions to fix %config at
http://public.kitware.com/Bug/view.php?id=10294. But I tried to use
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13348
==
Reported By:ergo1
Assigned To:
Hi list,
Current CMake Ninja generator will translate backslashes in the path
into forward slashes iff you are using MinGW(= Windows hosted Windows
compiler).
I feel this behavior should be default because Windows hosted
cross-compilers -- Android NDK for example -- also require this path
You are right,
in general backslashes as path separator are not needed on windows
except for cmd.ex cd buildin.
It is a quote character in strings and make always trouble on bash and
make!
Claus
On 22.06.2012, at 20:15, OKUMURA Yuki wrote:
Hi list,
Current CMake Ninja generator will
Hello Richard, What is the configured cutoff time for Nightly runs?Did you mean the nightly build time? During which hours does the "continuous" builder run?Between 6 am and 10 pm When does the "nightly" builder run?Nightly build time is configured for 23:00 UTC (11 pm) Which builds do you expect
Hi,
What is mentioned here has been implemented in our configuration system
(CMT previously implemented in pure C++/make and currently
re-implemented on top of CMake)
The principle is to add on top of the build system (say CMake, but this
could be plain make, or Waf) a layer that describes
Hello,
I have a problem using an OBJECT library that I want to compile into a SHARED
library using CMake version 2.8.8.
Here is a small example that demonstrates my problem:
# --- CMakeLists.txt ---
cmake_minimum_required(VERSION 2.8.8)
project(CMakeTest CXX)
Hello Benjamin,
if you wants to use an object file for a shared library, this object
file has to be compiled with -fPIC. I don't think, that it is possible
to create a shared library from such object files.
Regards,
Andreas
Am 22.06.2012 09:50, schrieb Benjamin Eikel:
Hello,
I have a
Hello Andreas,
Am Freitag, 22. Juni 2012, 11:09:36 schrieb Andreas Naumann:
Hello Benjamin,
if you wants to use an object file for a shared library, this object
file has to be compiled with -fPIC. I don't think, that it is possible
to create a shared library from such object files.
I know
I think the latter is the case. It should not be allowed to compose a
shared library from OBJECT libraries.
What does the cmake developer think about this problem?
Regards,
Andreas
Am 22.06.2012 11:14, schrieb Benjamin Eikel:
Hello Andreas,
Am Freitag, 22. Juni 2012, 11:09:36 schrieb Andreas
Hello, thanks for your reply. I saw that page already, and I understand
cmake needs to work around other people's mistakes, so the fix is not an
easy one.
My doubt is not about setting a specific path, but about the pdbs ending
up in the same spot. Is there any known problem with the pdbs
Hello, I need to add some linker dependencies to a static lib I'm
importing into our project. I need to do that on a per-target basis, but
the following is not working:
add_library(GameNet STATIC IMPORTED) # our code built in another project
and imported by the current one
add_library(Library
Hi Michele,
I don't know how it is in this particular case, but some
configuration-specific variable, property etc. names are
case-sensitive. I believe the default configuraions are called Debug
and Release. You could try setting
IMPORTED_LINK_INTERFACE_LIBRARIES_Debug.
Petr
On Fri, Jun 22,
On Jun 22, 2012, at 2:09 AM, NoRulez wrote:
Hello Richard,
What is the configured cutoff time for Nightly runs?
Did you mean the nightly build time?
I mean this value (for example in CTestConfig.cmake)
such as:
set(CTEST_NIGHTLY_START_TIME 21:00:00 EDT)
or
set(CTEST_NIGHTLY_START_TIME
I made a minor error in my previous posting. I forgot the first run as
continuous starts up on the second day.
I have make the correction inline below.
On Jun 22, 2012, at 2:09 AM, NoRulez wrote:
Hello Richard,
What is the configured cutoff time for Nightly runs?
Did you mean the nightly
Thanks for the suggestion. We just tried that but unfortunately it
doesn't change anything. Using IMPORTED_LINK_INTERFACE_LIBRARIES adds
the library to every target build, but either
IMPORTED_LINK_INTERFACE_LIBRARIES_DEBUG and
IMPORTED_LINK_INTERFACE_LIBRARIES_Debug seem to be just ignored.
Hi,
Perhaps this is a trivial question. Is there a way to return a specific error
code from a CMake script ( -P file option)? The only way I know to return a
failure is by calling message(FATAL_ERROR ...) and this returns rc = 1, but I
would like to return the error I got from the underlying
I tried this in my project. I added -fPIC to the COMPILE_FLAGS property of the
object library and it worked, but then you also get PIC static libraries (which
isn't that big of a deal). But time your compiles. Usually the compilation of
individual c files is well dominated by the linking time,
Presently, there is no way to do that. It would be a reasonable feature
request to add an EXIT_STATUS or EXIT_CODE parameter to the message
command to enable this functionality.
As an alternative (workaround), perhaps you could write the status value
into a file that you inspect after CMake
Thanks very much for you prompt answer.
As an alternative (workaround), perhaps you could write the status value into a
file that you inspect after CMake returns?
Unfortunately this is not possible because who calls by script is ctest.
Cheers,
Pere
On Fri, Jun 22, 2012 at 10:15 AM, Pere Mato Vila pere.m...@cern.ch wrote:
Thanks very much for you prompt answer.
As an alternative (workaround), perhaps you could write the status value
into a file that you inspect after CMake returns?
Unfortunately this is not possible because who
On Jun 22, 2012, at 4:25 PM, David Cole wrote:
As an alternative (workaround), perhaps you could write the status value into a
file that you inspect after CMake returns?
Unfortunately this is not possible because who calls by script is ctest.
Then it should definitely be possible.
I meant
Dependencies are between targets, not projects or CMakeLists.txt. You
would need to have a target in one project depend on a target defined
in another.
Some of these dependencies are managed automatically, as when you
build one or more libraries, and then reference them when you build a
program.
Hi Eli,
On 21 June 2012 21:25, Ateljevich, Eli e...@water.ca.gov 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
Say I have an ExternalProject that generates several libraries
ExternalProject_Add(foo
# the usual mumbo jumbo
)
set(foo_LIBRARIES)
# foo makes 3 libraries
foreach(lib a b c)
# import the libraries
add_library(${lib} STATIC IMPORTED)
# tell CMake where the library file is
Suppose I have two projects, A and B. A builds a shared lib that links with a
static lib in B.
Sometimes, I want to build and test B by itself. Other times I want to build
A, which requires building B.
For now, I manually (or with a script) build B, then set an environment
variable to say
Hi Leif.
I'm not on a machine with cmake now so I can't test, but I guess the
variable PROJECT_NAME is empty if no project() has been called yet.
Petr
On Fri, Jun 22, 2012 at 6:10 PM, Leif Walsh leif.wa...@gmail.com wrote:
Suppose I have two projects, A and B. A builds a shared lib that links
Hi,
On Fri, Jun 22, 2012 at 6:10 PM, Leif Walsh leif.wa...@gmail.com wrote:
Suppose I have two projects, A and B. A builds a shared lib that links
with a static lib in B.
Sometimes, I want to build and test B by itself. Other times I want to
build A, which requires building B.
For now,
On Fri, Jun 22, 2012 at 11:33 AM, Kent Williams
nkwmailingli...@gmail.comwrote:
Say I have an ExternalProject that generates several libraries
ExternalProject_Add(foo
# the usual mumbo jumbo
)
set(foo_LIBRARIES)
# foo makes 3 libraries
foreach(lib a b c)
# import the libraries
On Fri, Jun 22, 2012 at 12:10 PM, Leif Walsh leif.wa...@gmail.com wrote:
Suppose I have two projects, A and B. A builds a shared lib that links
with a static lib in B.
Sometimes, I want to build and test B by itself. Other times I want to
build A, which requires building B.
For now, I
That is very encouraging. I remembered getting problems but haven't tried on
2.8.8 yet I guess. Thanks, I'll try it soon.
Sent from my iPhone
On Jun 22, 2012, at 13:32, David Cole david.c...@kitware.com wrote:
On Fri, Jun 22, 2012 at 12:10 PM, Leif Walsh leif.wa...@gmail.com wrote:
OK, I guess.
The only reason I bring this up is ITK. If you're familiar with the
ITK build process, it has a 'module' concept -- not a module in the
CMake sense (where it is a library intended for runtime loading), but
in the sense that the build process is modular. Each of the ITK
libraries is
If CMake is running a script via -P, doesn't it return a non-zero
status if there's any error?
I'd think it would be sufficient to run to the end of the script if
everything works fine, but have something like
if(something_went_wrong)
message(FATAL_ERROR ¡OH NO! ¡SUCEDIO ALGO TERRIBLE!!!)
Ben,
Thanks. I saw -C but misunderstood it. It does fit well. For user acceptance,
the cache sytax would be preferable, but you can't have everything and I'm not
about to set it up as an elaborate workaround. The include solution I
quoted obviously assumed regular cmake syntax as well.
Hi all,
I am using cmake 2.8.8 under Fedora 17 64 bit, in which I have installed
ActiveTcl 8.6 in /opt.
My path variable starts with:
/opt/ActiveTcl-8.6/bin:...
And when I run tclsh/tclsh8.6/wish/wish8.6, I get the ActiveTcl one,
from /opt.
However, cmake does not find this Tcl/Tk
Have you tried setting CMAKE_PREFIX_PATH to /opt/ActiveTcl-8.6?
On Fri, Jun 22, 2012 at 3:43 PM, Georgios Petasis petas...@yahoo.gr wrote:
Hi all,
I am using cmake 2.8.8 under Fedora 17 64 bit, in which I have installed
ActiveTcl 8.6 in /opt.
My path variable starts with:
Hi again,
My project is set up so that the compiled targets naturally get output to a
structure that looks like a development mode installation:
/myproj
/build
/bin
/lib
/include
This is convenient for some users ... it is the sort of code people tinker
with, and I think a
No, I didn't know about this option. I tried it, and it does work.
Thank you,
George
Απο: David Cole david.c...@kitware.com
Προς: petas...@yahoo.gr
Κοιν.: cmake cmake@cmake.org
Στάλθηκε: 10:52 μ.μ. Παρασκευή, 22 Ιουνίου 2012
Θεμα: Re: [CMake] How to
I had this warning under Fedora 17, 64 bit:
-- Searching for Java...
CMake Warning at /usr/share/cmake/Modules/FindJava.cmake:120 (message):
regex not supported: java version 1.7.0_03-icedtea
OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64)
OpenJDK 64-Bit Server VM (build
I'm trying to build a find module to seek out the EGL library provided as
part of the Mali Developer Tool suite under win32.
The file I want is at C:/Program Files (x86)/ARM/Mali Developer
Tools/OpenGL ES Emulator v1.3.0
I cant for the life of me get it to succeed in finding the path. Am I
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 31b9aaf60da6eee0610b4a0347e58cbf7e68077e (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 51a05582f842f0b436381017219395ee899dedd9 (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index fecea12..2c69b95 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
SET(CMake_VERSION_MAJOR 2)
SET(CMake_VERSION_MINOR 8)
SET(CMake_VERSION_PATCH 8)
-SET(CMake_VERSION_TWEAK 20120622
43 matches
Mail list logo