On Mon, Oct 8, 2012 at 10:40 PM, James Bigler jamesbig...@gmail.com wrote:
In my project I need to manually link against a special version of
libstdc++, so I manually set the target link language to C and then add my
special library to the link line. On Linux this seems to work just fine,
On 10/09/2012 01:59 AM, James Bigler wrote:
On Mon, Oct 8, 2012 at 10:40 PM, James Bigler jamesbig...@gmail.com
mailto:jamesbig...@gmail.com wrote:
In my project I need to manually link against a special version of libstdc++
add_library(a SHARED a.cpp)
set_target_properties(a
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13579
==
Reported By:Jordan Lefebvre
Assigned To:
Hi all,
I have a question about tests of CMake itself. I'd like to create a new
feature patch and I would definitely want to supply tests with it. Is there
a standard mechanism (perhaps something like the macro check_cmake_test())
to test that a generated buildsystem (specifically, Visual Studio
On 10/09/2012 04:32 PM, Petr Kmoch wrote:
Is there a standard mechanism (perhaps something like the macro
check_cmake_test()) to test that a generated buildsystem (specifically,
Visual Studio solution)
contains what it should? If not, are there some test for this which I could
take
On Mon, Oct 8, 2012 at 10:40 PM, James Bigler jamesbig...@gmail.com wrote:
In my project I need to manually link against a special version of
libstdc++, so I manually set the target link language to C and then add my
special library to the link line. On Linux this seems to work just fine,
2012/10/9 James Bigler jamesbig...@gmail.com:
In my project I need to manually link against a special version of
libstdc++, so I manually set the target link language to C and then add my
special library to the link line. On Linux this seems to work just fine,
but on OSX it still add -lstdc++
2012/10/9 James Bigler jamesbig...@gmail.com:
I spent some time in the debugger to try and understand why CMake is making
the decisions it is. It comes down to this function which loops over all
the LinkClosures and calls AddImplicitLinkInfo for all languages that
*don't* match the language
At least for gcc I think you can fix this by passing
${OpenMP_CXX_FLAGS} to the linker as well (e.g. LINKER_FLAGS target
property).
-fopenmp at the link stage will instruct gcc to pass the appropriate
libraries to the linker.
Nils
On 10/08/2012 11:30 PM, Matthew Woehlke wrote:
When I write
On Tue, Oct 9, 2012 at 12:07 AM, Eric Noulard eric.noul...@gmail.comwrote:
2012/10/9 James Bigler jamesbig...@gmail.com:
In my project I need to manually link against a special version of
libstdc++, so I manually set the target link language to C and then add
my
special library to the
Hi,
I try to add all header files in the include directory so they are visible
in QTCreator.
My attempt looks like this.
file(GLOB Demo_HEADERS RELATIVE ${CMAKE_SOURCE_DIR}/include *.h)
message(STATUS )
message(STATUS ${Demo_HEADERS})
message(STATUS )
add_library(headers SHARED ${Demo_HEADERS}
Hi Witold.
Using RELATIVE does not change where the files are looked for, only how
they are reported. I believe you need this:
file(GLOB Demo_HEADERS RELATIVE ${CMAKE_SOURCE_DIR}/include include/*.h)
Hope this help.
Petr
On Tue, Oct 9, 2012 at 9:34 AM, Witold E Wolski wewol...@gmail.com
2012/10/9 James Bigler jamesbig...@gmail.com:
On Tue, Oct 9, 2012 at 12:07 AM, Eric Noulard eric.noul...@gmail.com
wrote:
2012/10/9 James Bigler jamesbig...@gmail.com:
In my project I need to manually link against a special version of
libstdc++, so I manually set the target link language
Thanks for the roses, Alex ;-)
On Monday, 8. October 2012, 20:24:32, Alexander Neundorf wrote:
Hi,
I just found this new page in the cmake wiki and I think this is very
useful information:
http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations
Please help keeping it up-to-date
Hi,
I have to get a build of my product on AIX 5.3 (powerpc) because of
backward compatibility concerns. The product builds fine on such a
system using conventional gmake. However, cmake fails to identify the
xlc/xlC compilers correctly and reports them as broken. What is the
way to fix this?
Hi Arindam,
Maybe you can try this way:
http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_use_a_different_compiler.3F
Xavier
On Tue, Oct 9, 2012 at 11:58 AM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
Hi,
I have to get a build of my product on AIX 5.3 (powerpc) because of
backward
On 8 October 2012 19:24, Alexander Neundorf a.neundorf-w...@gmx.net wrote:
Hi,
I just found this new page in the cmake wiki and I think this is very useful
information:
http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations
Looks great. I was looking for something like this recently.
On Tuesday, 9. October 2012, 12:25:51, Matt Williams wrote:
On 8 October 2012 19:24, Alexander Neundorf a.neundorf-w...@gmx.net wrote:
Hi,
I just found this new page in the cmake wiki and I think this is very
useful information:
http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations
On 10/09/2012 01:59 AM, James Bigler wrote:
On Mon, Oct 8, 2012 at 10:40 PM, James Bigler jamesbig...@gmail.com
mailto:jamesbig...@gmail.com wrote:
In my project I need to manually link against a special version of libstdc++
add_library(a SHARED a.cpp)
set_target_properties(a
Hello,
I am using find_package in Module mode for a Library that is also build
using cmake.
The Library is build in a way that it can be used both from the build
dir, and from the installed location.
When using find_package it always seems to prefer the build dir version,
which is somewhat
Hi,
On Tue, Oct 9, 2012 at 3:46 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
Hello,
I am using find_package in Module mode for a Library that is also build
using cmake.
The Library is build in a way that it can be used both from the build dir,
and from the installed location.
When
On 10/9/12 5:05 PM, Andreas Pakulat wrote:
Hi,
On Tue, Oct 9, 2012 at 4:42 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
On 10/9/12 4:12 PM, Andreas Pakulat wrote:
Hi,
On Tue, Oct 9, 2012 at 3:46 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
Hello,
I am using find_package in
On 10/9/2012 5:58 AM, Arindam Mukherjee wrote:
Hi,
I have to get a build of my product on AIX 5.3 (powerpc) because of
backward compatibility concerns. The product builds fine on such a
system using conventional gmake. However, cmake fails to identify the
xlc/xlC compilers correctly and reports
On Tue, Oct 9, 2012 at 9:21 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 10/9/2012 5:58 AM, Arindam Mukherjee wrote:
Hi,
I have to get a build of my product on AIX 5.3 (powerpc) because of
backward compatibility concerns. The product builds fine on such a
system using conventional
On 10/9/2012 3:06 PM, Arindam Mukherjee wrote:
On Tue, Oct 9, 2012 at 9:21 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 10/9/2012 5:58 AM, Arindam Mukherjee wrote:
Hi,
I have to get a build of my product on AIX 5.3 (powerpc) because of
backward compatibility concerns. The product
Hi,
On Tue, Oct 9, 2012 at 5:39 PM, Fabio Fracassi
fabio.fraca...@charite.de wrote:
On 10/9/12 5:05 PM, Andreas Pakulat wrote:
On Tue, Oct 9, 2012 at 4:42 PM, Fabio Fracassi
What do you mean with package registry here?
It means the package registry where cmake stores previously build
)
+set(CMake_VERSION_TWEAK 20121009)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
hooks/post-receive
--
CMake
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 8ee84adf9c644f3fda8825cced371d153d263db6 (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 1f3e010bd294fd0605a25a123579f407885e (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 f1049b9a3cf2975288b015ffa47b32228b07d9cc (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 aa0647ca9c28afb359066819f44eb101e42e8a2f (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 7da986bb6c3cb82a1853420377bb7be5fb581f81 (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 f413d280bc3f249d631c279d9dd236cbd85fd39d (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 76f3fe73baffd6b5b13e01d25e90789e84a38de8 (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 fb4de4495dbdde59b5fb210f0cbb835ebf5d7a6a (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 53c2dada1c4019ed21f14f33618a975a9652c84e (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 c8da8dd3a390010cd5e3038eb806376f244ba60d (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 3dd443b51026098eb4ec931ae8bb07f16abad37a (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 3c0dbc64cbed9139211d7e851d988fd117dfcf74 (commit)
via
39 matches
Mail list logo
