Hi,
I am using cmake 3.1.1 on my Windows 7 64bit system. I have Visual Studio
2013 installed.
The project I created with cmake works and can build with msbuild. But it
only build the x86 version. If I try:
msbuild /property:Platform=x64 myproj.vcproj
I got error says that the x64 profile
What is your cmake generator being used?
For Visual Studio 2013, you will need to use
cmake –G “Visual Studio 12 2013 Win64”
Scott
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Xi Shen
Sent: Thursday, April 23, 2015 11:28 PM
To: cmake@cmake.org
Subject: [CMake] cmake 3.1.1 does not
there's a 64 bit generator...
used to be a separate generator visual studio 12 2013 Win64 but it
doesn't show in the list of generators now...
On Thu, Apr 23, 2015 at 11:27 PM, Xi Shen davidshe...@gmail.com wrote:
Hi,
I am using cmake 3.1.1 on my Windows 7 64bit system. I have Visual Studio
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15531
==
Reported By:Bjoern Thiel
Assigned To:
Hello,
I use the ExternalProjet_Add function to download and install third-party
libraries.
Here is an example of a CMakeLists file containing such a call:
=
cmake_minimum_required (VERSION 2.6)
project (example CXX)
set(CMAKE_VERBOSE_MAKEFILE ON)
Ah~, so it's a hidden feature? OK, I will give a try.
Thanks,
David
On Fri, 24 Apr 2015 16:38 J Decker d3c...@gmail.com wrote:
there's a 64 bit generator...
used to be a separate generator visual studio 12 2013 Win64 but it
doesn't show in the list of generators now...
On Thu, Apr 23, 2015
How do you do step 3) -- build boost?
Unless the build is done and installed and ready to find before the
end of step 3, there is still nothing (yet) there for the find_package
in step 4 to find...
David C.
On Fri, Apr 24, 2015 at 9:36 AM, matzeNOTAVAILABLE . matze...@gmail.com wrote:
Hi,
i
Hi,
i am struggling somewhat with find_package. I looked at the documentation
and googled quite a bit, but i am still stuck. I alos tried stackoverflow
to no avail.
What i am trying to accomplish is the following:
1) See if my custom boost installation exists (using find_package)
(version 1.57)
We really shouldn't have removed the explicit mention of the Win64
suffixed generator names in the list of generators in --help ouput...
That was a mistake.
We should put it back.
On Fri, Apr 24, 2015 at 5:29 AM, Xi Shen davidshe...@gmail.com wrote:
Ah~, so it's a hidden feature? OK, I will
Excellent. Thanks for the pointer... I had not seen that recent commit.
Seems we had a shared this should be explained better so we don't get
so much email about it brain wave pattern.
Happy Friday,
D
On Fri, Apr 24, 2015 at 9:04 AM, Nils Gladitz nilsglad...@gmail.com wrote:
On 04/24/2015
On 04/24/2015 02:22 PM, David Cole via cmake-developers wrote:
We really shouldn't have removed the explicit mention of the Win64
suffixed generator names in the list of generators in --help ouput...
That was a mistake.
We should put it back.
As I understand it the generator suffixes aren't
Hi Matt,
1) (... set boost_root ...)
2) FIND_PACKAGE(Boost 1.57 COMPONENTS log thread filesystem system)
If you're using CMake = 3.0, then there's a Boost_NAMESPACE variable you
can set that will cause the find module look for mangled library names line
myboostnamespace_datetime instead of
You should keep replies on the mailing list so others can see it, and
pitch in and help.
If you are actually building boost using execute_process during a
CMake run, then it should be able to find it with your find_package
call. Perhaps you need to give the find_package in step 4 a hint to
find
I don't like my current solution for such problem, but it works for me
well. Note file(GLOB_RECURSE ... and custom copy step in the end.
Also you can try to google cmake super build which probably will
provide you more ideas.
include(ExternalProject)
set(WEBSOCKETS_PATCH_DIR
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15534
==
Reported By:James Bigler
Assigned To:
Le 22/04/15 23:46, Domen Vrankar a écrit :
Hi,
I just installed a virtual machine running Debian 7.8.0, and everything
worked like a charm from the first run. I did that in the two following way:
- sourced my branch
https://github.com/raffienficiaud/CMake/tree/cpack_deb_refactoring
- I also
Le 22/04/15 08:01, Domen Vrankar a écrit :
2015-04-21 23:38 GMT+02:00 Raffi Enficiaud raffi.enfici...@mines-paris.org:
Le 21/04/15 23:01, Domen Vrankar a écrit :
There are a few other things to change though.
Take a look at CPackRPM man page:
Le 22/04/15 08:01, Domen Vrankar a écrit :
2015-04-21 23:38 GMT+02:00 Raffi Enficiaud raffi.enfici...@mines-paris.org:
Le 21/04/15 23:01, Domen Vrankar a écrit :
Hi,
I pushed your first patch to next (I've split it into two separate
commits and made some minor cleanup changes):
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15533
==
Reported By:trsystran
Assigned To:
20150424)
+set(CMake_VERSION_PATCH 20150425)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
Hello,
would it be possible to add generator expression support to CPack
so that I can use $CONFIG within CPACK_PACKAGE_FILE_NAME? I'm
using the CPack module from within my CMakeLists.txt.
I'm trying to generate unique file names per architecture and
configuration but multi config generators
The Fedora packager of PLplot is having trouble splitting installed
results into separate binary packages because of the way that PLplot
currently exports its targets. What steps do we have to do to make
life easier for him?
Here is the typical code we use now to export our targets.
# Done
Hi,
On 23/04/15 16:54, Mateusz Loskot wrote:
Surprisingly, I'm having trouble to figure out how to determine,
that in Linux 64-bit OS, I'm building a project with -m32 specified.
IOW, any CMake variable or macro to tell me target architecture
of a build that is being configured is 32 or 64
On 24.04.2015 20:55, Gregor Jasny wrote:
Hello,
would it be possible to add generator expression support to CPack
so that I can use $CONFIG within CPACK_PACKAGE_FILE_NAME? I'm
using the CPack module from within my CMakeLists.txt.
I'm trying to generate unique file names per architecture and
It would be really nice if the docs like:
http://www.cmake.org/cmake/help/v3.2/module/CheckCXXSourceCompiles.html
would indicate what version of cmake it was added in.
Is this recorded anywhere?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA
This new policy breaks a long standing feature of FindCUDA.
Basically I could add the MAIN_DEPENDENCY to all CUDA files built. If the
same CUDA file was used in multiple custom commands it would attach the
build rule to the first command, and leave the remaining ones as phantom
.rule files in
26 matches
Mail list logo
