Is the intention of CMAKE_[C|CXX]_COMPILER_VERSION to check the [C|C
++]-compiler version platform independent?
Greetings
Micha
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check
Hi, there!
I am using Windows SDK 7.1 + nmake + CMake for building Windows
applications.
Follow these:
http://www.cmake.org/pipermail/cmake/2009-April/028668.html
http://msdn.microsoft.com/en-us/library/bb385193.aspx
I can't make /MP option works after this change in CMake's main
CMakeLists.txt
>
On 19.09.2012 08:08, Wouter van Kleunen wrote:
Peter,
i had 2.8.9-pre3 before, i upgraded to 2.8.9. But only after deleting
the CMakeLists user file from qtcreator, deleting the build directory
and restarting qtcreator I was able to get the option to build with Ninja.
Anyway, it seems to work
When I invoke cmake for the first time in a project, I normally use
-DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
I'm tired of typing that every time I blow away my CMakeCache.txt. Is
there a place I can register these preferences so I don't have to?
Thanks,
--
Dave Abrahams
Boo
2012/9/20 Dave Abrahams :
>
> When I invoke cmake for the first time in a project, I normally use
>
> -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
>
> I'm tired of typing that every time I blow away my CMakeCache.txt. Is
> there a place I can register these preferences so I don't hav
On 09/20/2012 02:10 PM, Dave Abrahams wrote:
When I invoke cmake for the first time in a project, I normally use
-DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
I'm tired of typing that every time I blow away my CMakeCache.txt. Is
there a place I can register these preferences so I
Am 2012-09-20 15:10, schrieb Dave Abrahams:
When I invoke cmake for the first time in a project, I normally use
-DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
I'm tired of typing that every time I blow away my CMakeCache.txt.
Is
there a place I can register these preferences so I
Hello list
I have a problem finding a dependent library of my own libsieve.so:
set(CPPLIB_DIR "${CMAKE_SOURCE_DIR}/../core/build")
find_library(CPPLIB_SIEVE_LIBRARY NAMES libsieve PATHS CPPLIB_DIR)
I have the following folder structure:
core
build
libsieve.so
project
CMakeLists.txt
It
On Thursday 20 September 2012 17:25:35 Reza Housseini wrote:
> set(CPPLIB_DIR "${CMAKE_SOURCE_DIR}/../core/build")
> find_library(CPPLIB_SIEVE_LIBRARY NAMES libsieve PATHS CPPLIB_DIR)
Use instead sieve for your library name. Also, check with
message(${CPPLIB_DIR})
the path to your library
--
Bo
Hi Yuchen,
we're using the same way to enable /MP, and it works for us. You didn't say exactly what doesn't
work, so I'm left to guessing.
Have you checked in Visual Studio if the flag is set (Project properties->C/C++->Command Line)?
Maybe there's a conflicting option enabled? Or maybe you'r
On Thursday 20 September 2012, Rui Maciel wrote:
> On 09/20/2012 02:10 PM, Dave Abrahams wrote:
> > When I invoke cmake for the first time in a project, I normally use
> >
> > -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
> >
> > I'm tired of typing that every time I blow away my CM
On Thursday 20 September 2012, Rolf Eike Beer wrote:
> Am 2012-09-20 15:10, schrieb Dave Abrahams:
> > When I invoke cmake for the first time in a project, I normally use
> >
> > -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
> >
> > I'm tired of typing that every time I blow away my
nmake does not do parallel builds. Try using jom.
http://blog.qt.digia.com/2009/03/27/speeding-up-visual-c-qt-builds/
http://qt-project.org/wiki/jom
/MP only works from the VS IDE.
On 9/20/2012 11:34 AM, Andreas Haferburg wrote:
Hi Yuchen,
we're using the same way to enable /MP, and it wor
Thanks for that - I will try it again with the 2.8.10 release candidate.
--
Glenn
On 18 September 2012 22:17, David Cole wrote:
> On Mon, Sep 17, 2012 at 1:02 PM, Glenn Coombs wrote:
>
>> Hi,
>>
>> I just installed the Visual Studio 2012 Express edition for Windows
>> Desktop and cmake 2.8.9 i
Alexander Neundorf wrote:
> On Thursday 20 September 2012, Rolf Eike Beer wrote:
> > Am 2012-09-20 15:10, schrieb Dave Abrahams:
> > > When I invoke cmake for the first time in a project, I normally use
> > >
> > > -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
> > >
> > > I'm tired o
I'm building for Raspberry Pi - which is embedded Linux on Arm, distro
is Debian-based.
I'm getting this linker error:
libzmq.a(libzmq_la-clock.o): In function `zmq::clock_t::now_us()':
/home/pi/git/libzmq/src/clock.cpp:76: undefined reference to `clock_gettime'
I believe I need to add "-lrt", I
The Info.plist for CMake 2.8-9.app has an empty string for CFBundleName,
making it show up without a name in utilities such as Activity Monitor.
It's also bad that there is an empty string for CFBundleIdentifier,
CFBundleVersion, CFBundleShortVersionString, CFBundleGetInfoString, and
NSHumanRe
On Thu, 20 Sep 2012 11:36:53 -0700, James Walker said:
>The Info.plist for CMake 2.8-9.app has an empty string for CFBundleName,
>making it show up without a name in utilities such as Activity Monitor.
> It's also bad that there is an empty string for CFBundleIdentifier,
>CFBundleVersion, CFBu
Hi All,
Just yesterday, Apple released new "Command Line Tools for XCode 4.5".
Unlike their previous command-line compiler tools, these new tools no
longer require XCode. They are stand-alone. This is great, because
the package is just 110MB (compared to 1560MB for XCode).
However, there is a
I use the following macro in my own projects:
#---
# This macro will set all the variables necessary to have a "good" OS X
Application
# bundle. The variables are as follows:
# PROJECT_NAME - which can be taken from the
On Sep 20, 2012, at 4:26 PM, David Gobbi wrote:
> Hi All,
>
> Just yesterday, Apple released new "Command Line Tools for XCode 4.5".
> Unlike their previous command-line compiler tools, these new tools no
> longer require XCode. They are stand-alone. This is great, because
> the package is jus
On Thu, 20 Sep 2012 14:26:54 -0600, David Gobbi said:
>Hi All,
>
>Just yesterday, Apple released new "Command Line Tools for XCode 4.5".
> Unlike their previous command-line compiler tools, these new tools no
>longer require XCode. They are stand-alone.
You sure? I'm pretty sure the 4.4 command
On Thu, 20 Sep 2012 16:40:20 -0400, Michael Jackson said:
>I use the following macro in my own projects:
Perhaps you are in a position to make a patch to fix CMake.app itself? :)
Cheers,
--
Sean McBride, B. Eng s...@r
On 9/20/2012 12:38 PM, Sean McBride wrote:
On Thu, 20 Sep 2012 11:36:53 -0700, James Walker said:
The Info.plist for CMake 2.8-9.app has an empty string for CFBundleName,
making it show up without a name in utilities such as Activity Monitor.
It's also bad that there is an empty string for CF
On Thu, Sep 20, 2012 at 2:55 PM, Sean McBride wrote:
> On Thu, 20 Sep 2012 14:26:54 -0600, David Gobbi said:
>
>>Hi All,
>>
>>Just yesterday, Apple released new "Command Line Tools for XCode 4.5".
>> Unlike their previous command-line compiler tools, these new tools no
>>longer require XCode. The
On Thu, 20 Sep 2012 16:16:19 -0600, David Gobbi said:
>> You sure? I'm pretty sure the 4.4 command line tools didn't need
>Xcode.app either.
>
>Could be. I'm still using XCode 3.2 on my own box. It's the people
>working under me who are using newer versions.
A! :) I think it's been this w
Hello,Andreas!
Thanks for your comments. I am working in command line, use nmake.
So In here does not exist any Visual IDE stuff.
2012/9/20 Andreas Haferburg
> Hi Yuchen,
>
> we're using the same way to enable /MP, and it works for us. You didn't
> say exactly what doesn't work, so I'm left to g
As I know, qmake support /MP on command line builds after set ENV CL=/MP,
and nmake can do parallel builds.
Follow the MS docs:
cl a.cpp b.cpp c.cpp /MP should works well on command line.
Seems CMake does not implements this.
So, can I request a feature for this?
2012/9/21 Bill Hoffman
> nmake d
On Thu, Sep 20, 2012 at 5:32 PM, Bogdan Cristea wrote:
> On Thursday 20 September 2012 17:25:35 Reza Housseini wrote:
>> set(CPPLIB_DIR "${CMAKE_SOURCE_DIR}/../core/build")
>> find_library(CPPLIB_SIEVE_LIBRARY NAMES libsieve PATHS CPPLIB_DIR)
>
> Use instead sieve for your library name. Also, chec
29 matches
Mail list logo