Just remove these values from cache. If you always want to search in custom
location, look at find_package's options to avoid searching in default
locations
On Apr 11, 2011 6:03 PM, Martin Vymazal martin.vyma...@vki.ac.be wrote:
Hello,
I'm a beginner and I apologize in case I'm asking a
Hi all,
I got a simple question,
What is idea behind target property LINK_FLAGS?
When I add linker flag e.g --no-undefined then cmake is not alligning
it to real linker that will be used during linking.
for example --no-undefined is a valid ld switch, but when I specify it
LINK_FLAGS it will
On 04/18/2011 03:25 PM, Łukasz Tasz wrote:
Hi all,
I got a simple question,
What is idea behind target property LINK_FLAGS?
When I add linker flag e.g --no-undefined then cmake is not alligning
it to real linker that will be used during linking.
for example --no-undefined is a valid
The 3rd party libs should not be rebuilding if there are no source files
changing... We do this all the time around here, and I have not heard
anybody else complaining about this problem.
Is your project publicly available so that we may try to reproduce this
behavior here...?
On Fri, Apr 15,
Hello Yuri,
thanks for the hint. I'll test as soon as I get back to my work
computer. Thank you.
Martin Vymazal
Quoting Yuri Timenkov y...@timenkov.ru:
Just remove these values from cache. If you always want to search in custom
location, look at find_package's options to avoid
greetings,
It so happens that i want to find the configure specs for the paraview
build that they have installed on the cluster here; is it possible to
get this info using ccmake? they have changed the source dir, so running
ccmake pointing to it is not really possible (i found out this when i
I got a simple question,
What is idea behind target property LINK_FLAGS?
When I add linker flag e.g --no-undefined then cmake is not alligning
it to real linker that will be used during linking.
for example --no-undefined is a valid ld switch, but when I specify it
LINK_FLAGS it will not
Hello,
when we were considering to use D for our multi-platform project we
did some research about appropriate build system and ended with the
two: waf cmake with more preference for the latter due to its
ability to create binary packages for Mac and Windows (afaik, using
NSIS installer) with
Am Montag 18 April 2011, 15:25:24 schrieb Łukasz Tasz:
Hi all,
I got a simple question,
What is idea behind target property LINK_FLAGS?
When I add linker flag e.g --no-undefined then cmake is not alligning
it to real linker that will be used during linking.
for example --no-undefined
Hi,
Of course I read manual. But I'm a little bit confused. That's why I'm
asking about idea behind LINK_FLAGS,
Cmake is not consequent because when I'm adding:
add_library(test foo.cxx bar.cxx)
SET_TARGET_PROPERTIES( test PROPERTIES SOVERSION 1.2 VERSION 1.1)
it 'magicaly knows' how to build
I've been trying most things I can think of, but have been unable to
come up with a solution.. the basic gist is I need to change the compile
flags for a SINGLE file within a project. Specifically, disabling all
compile warnings for that file.
add_definitions() seems to effect the whole
On Monday 18 April 2011, The Novice Coder wrote:
I've been trying most things I can think of, but have been unable to
come up with a solution.. the basic gist is I need to change the compile
flags for a SINGLE file within a project. Specifically, disabling all
compile warnings for that
On 04/18/2011 07:37 PM, Łukasz Tasz wrote:
Hi,
Of course I read manual. But I'm a little bit confused. That's why I'm
asking about idea behind LINK_FLAGS,
Cmake is not consequent because when I'm adding:
add_library(test foo.cxx bar.cxx)
SET_TARGET_PROPERTIES( test PROPERTIES SOVERSION
On Mon, 18 Apr 2011 21:52:31 +0200, Alexander Neundorf wrote:
On Monday 18 April 2011, The Novice Coder wrote:
I've been trying most things I can think of, but have been unable
to
come up with a solution.. the basic gist is I need to change the
compile
flags for a SINGLE file within a
Hi everyone,
I'd like to be able to use ctest to run tests which satisfy more than one label
property. E.g. the intersection of multiple test selections created with -L.
Is there a straightforward way to do this though ctest? Do the regular
expressions that ctest uses for matching have an
Hi everybody,
I was wondering if anyone has run into the following problem. With version
2.8.2 of cmake, the project generated for C::B included the tree of the src
files starting at the base of the project. However, I've upgraded to cmake
2.8.4, and the tree starts from /, which is driving
Am 18.04.2011 06:58, schrieb Michael Hertling:
On 04/16/2011 12:05 AM, Oliver Buchtala wrote:
Am 15.04.2011 23:48, schrieb Michael Hertling:
On 04/15/2011 11:22 PM, Oliver Buchtala wrote:
Hi,
I observe that a custom command attached to a custom target as
POST-BUILD is launched on every
On 04/19/2011 02:17 AM, Oliver Buchtala wrote:
Am 18.04.2011 06:58, schrieb Michael Hertling:
On 04/16/2011 12:05 AM, Oliver Buchtala wrote:
Am 15.04.2011 23:48, schrieb Michael Hertling:
On 04/15/2011 11:22 PM, Oliver Buchtala wrote:
Hi,
I observe that a custom command attached to a custom
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 f7e0ea7b6ee08178dcdbba9ccbdff3426494ecdc (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, master has been updated
via b1a9f7a2758b5be3aea03e0fa75daee7d8179684 (commit)
from
20 matches
Mail list logo