, 2018 at 12:54 AM Eric Noulard wrote:
>
>
> Le mar. 4 déc. 2018 à 06:11, James Bigler a
> écrit :
>
>> Unfortunately I don't think your suggestion will work.
>>
>> I need to invoke a custom executable to build my project and not a
>> msproject. I also nee
ke.org/cmake/help/latest/command/include_external_msproject.html
>
> wouldn't be better in your case?
>
>
> Le mar. 4 déc. 2018 01:43, James Bigler a écrit :
>
>> I have an external project that I would like to compile using their build
>> system, and be able
I have an external project that I would like to compile using their build
system, and be able to set the VS_COMMAND to the result of the project so I
can run it.
add_custom_target(${cmake_target}
COMMAND make mytarget ${BUILD_ARGS}
COMMAND ${CMAKE_COMMAND} -E
Will changes integrated into master automatically be slated for either
v3.5.0 RC2 or v.3.5.0 final?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
ow.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=59535a60761ca79e685e24f18bbd621e70d0594b
commit 59535a60761ca79e685e24f18bbd621e70d0594b
Merge: bd6a289 e739ef7
Author: James Bigler <jamesbig...@gmail.com>
AuthorDate: Mon Feb 8 15:40:22 2016 -0500
Commit:
ow.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42416ba1798a81bd3d0e9aeb9919dc3e3de3c603
commit 42416ba1798a81bd3d0e9aeb9919dc3e3de3c603
Merge: 7885d80 4b561b4
Author: James Bigler <jamesbig...@gmail.com>
AuthorDate: Fri Feb 5 16:36:23 2016 -0500
Commit:
ow.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b11b9d05dd1d9e77ac76f6b9b72c4f1face53418
commit b11b9d05dd1d9e77ac76f6b9b72c4f1face53418
Merge: 42416ba 81ecc72
Author: James Bigler <jamesbig...@gmail.com>
AuthorDate: Fri Feb 5 16:51:26 2016 -0500
Commit:
If I specify an empty value for filename, I get the behavior of relative
path, and var turns into CMAKE_CURRENT_SOURCE_DIR. It seems like if I put
an empty file I should get back an empty output.
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Say you have a simple cpp file:
cat > test.cpp
int main() { return 0; }
Then you have this as your CMakeLists.txt file:
set(input_file test.cpp)
set(generated_file
${CMAKE_CURRENT_BINARY_DIR}/${input_file}.blah${CMAKE_CXX_OUTPUT_EXTENSION})
add_custom_command(
OUTPUT ${generated_file}
Has anyone been able to use the /Zo flag? I tried to add it to my
RelWithDebInfo build, but the flag doesn't seem to be showing up in the
command line (in the GUI).
My flags are:
/MT /O2 /Ob2 /D NDEBUG /Zi /Zo
I'm using cmake 3.2.1.
Documentation on /Zo (available in VS2013.3+:
t; section in the "Command Line" section
of the project settings.
On Mon, Dec 14, 2015 at 4:35 PM, James Bigler <jamesbig...@gmail.com> wrote:
> Has anyone been able to use the /Zo flag? I tried to add it to my
> RelWithDebInfo build, but the flag doesn't seem to be
" following
> that can be done before any build.)
>
> It would be nice if the CUDA dependency generation worked like regular
> cpp file dependency generation so that cmake would be run only upon
> change of files and that otherwise it did not have to be turned off
> completely
This could be caused by CUDA generating dependencies and then needing to
load them at the next configure step.
For our automated builds, where we don't rely on dependencies during
development (e.g. build one main target from scratch then throw it away),
we set the CMAKE_SUPPRESS_REGENERATION
a runtime variable.")
> endif()
> endif()
> ...
> macro(cuda_unset_include_and_libraries)
> ...
> if(NOT CUDA_USE_STATIC_CUDA_RUNTIME_FORCED )
> unset(CUDA_USE_STATIC_CUDA_RUNTIME CACHE)
> endif()
> endmacro()
>
>
> Le lun. 12 oct. 2015 à 14:32, James Bigler <jamesbi
Whether you can use the static runtime is based on the toolkit found, so if
you change the toolkit (checked with the CUDA_TOOLKIT_ROOT_DIR_INTERNAL
variable) we need to reset all dependent values.
I don't see a clean way to get this to work in the way you want. The
script can't tell the
I want to have some files show up in the IDE. I know I can add files to
targets, but the problem is these files don't belong to a particular
target. It would be nice to have them show up in a folder (similar to how
the target FOLDER property or source_group function works).
Is this possible?
Is it possible to set the generated file's executable permissions when
using file(GENERATE)? I'm trying to generate shell scripts, and I want the
executable bit set.
Thanks,
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
list(APPEND) requires at least one element argument, right?
Can you require the same thing for string(APPEND)? That would make it
symmetric and remove your edge case.
On Mon, Jul 6, 2015 at 2:47 PM, Daniel Pfeifer dan...@pfeifer-mail.de
wrote:
On Mon, Jul 6, 2015 at 8:41 PM, Brad King
I looked at it briefly one day, and I couldn't figure out a way to tie the
output of custom commands to the list of objects that add_library(OBJECTS)
produces.
Alternatively since all you want is a list of objects, FindCUDA can produce
this just as well.
Use the CUDA_WRAP_SRCS macro. It
The issue is that nvcc doesn't accept host compiler flags that are C++
only. It does understand a version of the command directly (-std c++11).
There should be a fix for this in TOT. See if you can grab a nightly and
test it out.
James
On Mon, May 11, 2015 at 10:54 AM, Wesley Smith
OK, thanks.
I still think that if there is a difference in behavior for Makefile
generators between MAIN_DEPENDENCY and DEPENDENCY there is a bug in CMake.
Perhaps there needs to be bug filed for that. Here's the documentation:
In makefile terms this creates a new target in the following form::
...@gmail.com wrote:
On 04/27/2015 11:48 PM, James Bigler wrote:
The problem is the current detection only barfs (unless I missed
something - please correct if I'm wrong). What we need is detection and
adaptation. Rather than telling the user, DON'T DO THAT! we should be
helping the user
From what I understand the only time this really became a problem was when
there were multiple instances of MAIN_DEPENENCY across multiple targets.
If done within a single target CMake did the right thing and only attached
the first build rule.
The issue really seems to be related to multiple
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
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b63f40e4c616204ff4950163728dd1951eb86f6a
commit b63f40e4c616204ff4950163728dd1951eb86f6a
Merge: 88d5275 e88217c
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Mon Apr 20 14:39:58 2015 -0400
Commit: CMake Topic Stage
FindCUDA doesn't look for a specific version, but rather checks to see if
the version it found is the one you asked for. You can set the
CUDA_TOOLKIT_ROOT_DIR to the one you want (and reconfigure - I've set it up
to easily change this), or you can change your environment in Windows to
point to
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7fbfea4b7571b9eae5819d73d866ee2e4f26714b
commit 7fbfea4b7571b9eae5819d73d866ee2e4f26714b
Merge: fc2f2bd 6b29185
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Wed Apr 8 15:53:58 2015 -0400
Commit: CMake Topic Stage
311d1653f9f79a4fe719491a116425aa56d95f78
Merge: f920f7e f0614dd
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Wed Apr 8 17:11:49 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Apr 8 17:11:49 2015 -0400
Merge topic 'FindCUDA.cmake/CUDA_SOURCE_FILE
, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e409a8953a09e2a20428a6613115eb124796f808
commit e409a8953a09e2a20428a6613115eb124796f808
Merge: baadaeb 57661fe
Author: James Bigler jamesbig...@gmail.com
AuthorDate
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fdf5e062c75d6d55f8e8fa8f3f6dd0efe3663340
commit fdf5e062c75d6d55f8e8fa8f3f6dd0efe3663340
Merge: 82c65ba 06fa63d
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Thu Apr 2 19:12:56 2015 -0400
Commit: CMake Topic Stage
I have a topic that I pushed to stage, so someone else could take a look.
At this point, it needed some fixing, so I made some changes to my local
topic and pushed those back to the same topic. When I push the topic into
next and the testing passes, what checkin string will be used for change
On Sat, Jan 17, 2015 at 8:13 AM, Adam Strzelecki o...@java.pl wrote:
1. Support for dependency scanning. If I change a header included by
file.cu I want file.cu to be recompiled. This is easy for makefiles,
hard for anything else.
.cu is superset of C++ so it should be pretty easy to get
On Fri, Jan 16, 2015 at 9:25 AM, Irwin Zaid irwin.z...@physics.ox.ac.uk
wrote:
Hi all (and James),
I just have two other quick questions about FindCUDA. Here we go!
1) I have a project that tries to keep all its CUDA code in .cpp files.
I'm currently making this work with a lot of dummy .cu
On Fri, Jan 16, 2015 at 10:15 AM, Irwin Zaid irwin.z...@physics.ox.ac.uk
wrote:
Hi James,
Thanks for the quick reply. Some thoughts...
FindCUDA only looks for .cu files. In CUDA_WRAP_SRCS:
get_source_file_property(_is_header ${file} HEADER_FILE_ONLY)
if(${file} MATCHES \\.cu$ AND NOT
On Fri, Jan 16, 2015 at 6:46 AM, Brad King brad.k...@kitware.com wrote:
On 01/16/2015 06:54 AM, Adam Strzelecki wrote:
Hi. It makes me curious why CUDA support is not just implemented
as compiler via proper CMakeDetermineCUDACompiler
I don't think there is any reason besides no one doing
its flags to the intermediate link file. Did you mean to
put message commands into CUDA_LINK_SEPARABLE___COMPILATION_OBJECTS
itself? When I put them into my main CMakeLists.txt, nothing is
printed for ${nvcc_flags} or the other variables.
James Bigler wrote:
On Tue, Jan 6
to get -fPIC passed to the
intermediate linking? Am I meant to always build in Debug mode just for
that?
Irwin
Irwin Zaid wrote:
I just double-checked. The -fPIC is definitely there for each individual
object file, but not for the *_intermediate_link.o.
Irwin
James Bigler wrote:
James
I've pushed a change into 'stage' [1] that I hope to get into 'next'
(something isn't working with my ssh authentication).
James
[1] commit b4e54f9b8c748f78d16e9da055a7e0436d7654ef
Author: James Bigler @
Date: Tue Jan 6 16:28:05 2015 -0700
FindCUDA: Add relevant CMAKE_{C,CXX}_FLAGS
On Tue, Jan 6, 2015 at 8:54 AM, Irwin Zaid irwin.z...@physics.ox.ac.uk
wrote:
Okay, an update on this.
2) This is trickier and, unfortunately, still not working. We are already
adding -fPIC to CMAKE_CXX_FLAGS, should that not be enough? I also tried
adding it to both CMAKE_CXX_FLAGS_DEBUG
commands into CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS itself? When I put
them into my main CMakeLists.txt, nothing is printed for ${nvcc_flags} or
the other variables.
James Bigler wrote:
On Tue, Jan 6, 2015 at 8:54 AM, Irwin Zaid irwin.z...@physics.ox.ac.uk
mailto:irwin.z
On Mon, Jan 5, 2015 at 1:57 PM, Irwin Zaid irwin.z...@physics.ox.ac.uk
wrote:
Hi James,
Thanks for the quick reply! As I mentioned, we've hit two issues. The
first is the project dependencies one, which I'll try and describe more a
bit below. I'm not a CMake expert, so please bear with me.
and, indeed, the *_intermediate_link.o file is not being
passed -fPIC. Is this our problem? What is the correct fix?
Irwin
James Bigler wrote:
On Mon, Jan 5, 2015 at 1:57 PM, Irwin Zaid irwin.z...@physics.ox.ac.uk
mailto:irwin.z...@physics.ox.ac.uk wrote:
Hi James,
Thanks
The only CMake build dependency changes when doing separable compilation
are found in CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS. Basically what this
does is create a new rule to build an intermediate link file. For
everything but some versions of MSVC generators it adds a custom command to
If I have a file that depended on another file (say file.cpp includes a.h
which includes b.h), and then I rename b.h to c.h is CMake able to detect
that b.h no longer exists on disk and remove the dependency from the
makefiles?
Right now the makefile still has a dependency to b.h which it cannot
cuda_add_executable(mytarget foo.cc OPTIONS -x cu)
Unfortunately, FindCUDA is setup to ignore any files that aren't .cu files.
CUDA_WRAP_SRCS()
...
foreach(file ${ARGN})
# Ignore any file marked as a HEADER_FILE_ONLY
get_source_file_property(_is_header ${file} HEADER_FILE_ONLY)
or makefile) just to
compile these rules.
On Tue, Mar 5, 2013 at 11:10 AM, Brad King brad.k...@kitware.com wrote:
On 03/05/2013 10:27 AM, Brad King wrote:
On 12/04/2012 07:30 PM, James Bigler wrote:
Is there something CMake can do to correct this error/bug with VS 2010?
I've narrowed this case
Could someone please explain to me why we need to change all the if
statements to look super ugly?
Expanding WIN32 to dereference the value is just a recipe for confusion.
Honestly I would prefer if there was a policy to never deference variables
in if statements and replace the if's with:
if
Is there an equivalent command to link_directories that support generator
expressions?
link_directories(
$$CONFIG:Debug:${PROG_LIBRARY_DIRS_RELWITHDEBCRT} )
link_directories( $NOT:$CONFIG:Debug:${PROG_LIBRARY_DIRS} )
Basically I want to use PROG_LIBRARY_DIRS_RELWITHDEBCRT for Debug
The CUDA_NVCC_FLAGS variable is a list not a string. You also have to turn
CUDA_SEPARABLE_COMPILATION on.
Try this
list(APPEND CUDA_NVCC_FLAGS -gencode arch=compute_30,code=sm_30 -rdc=true)
set( CUDA_SEPARABLE_COMPILATION ON)
On Thu, Jul 17, 2014 at 8:07 AM, Notargiacomo Thibault
That work around seems to only be useful if you wish to modify all the find
modules you wish to use.
Is there a CMake variable you could set that would allow all the
find_{include,library,path} functions within modules to pick up the HINT'ed
path first then search the system paths?
On Tue, Jun
Are there some good examples of why one would use bracket arguments? I'm
trying to understand the anticipated use cases. The bracket comments are
great for a /**/ substitute.
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=15db64e834f175212e4204928c19b3738e1fad3c
commit 15db64e834f175212e4204928c19b3738e1fad3c
Merge: 83d9bf1 26b4b63
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Sun May 18 02:32:01 2014 -0400
Commit: CMake Topic Stage
What do I do if I have a patch I want to go to next, but origin/master is
broken? I'm supposed to create branches off of origin/master then merge
them into next, but I can't verify that my fix works.
For details about the break see my email on May 8th regarding external
object files not being
I was planning on fixing a bug related to flags and separable compilation
for FindCUDA when I discovered something peculiar. I'm asking here in case
I missed something with how source files are processed.
I branched off of origin/master this morning.
I have a macro that generates some custom
This is also causing my CUDA separable compilation feature to break as well.
I'm adding object files to the source list of a target, and this works in
certain situations, but not all.
James
From: jamesbig...@gmail.commailto:jamesbig...@gmail.com
-Original Message-
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On
Behalf Of Brad King
Sent: Wednesday, April 23, 2014 11:06 AM
To: cmake-developers@cmake.org
Subject: Re: [cmake-developers] CMP0043 warnings everywhere
On 04/23/2014 12:57 PM, James Bigler
I'm getting tons of CMP0043 warnings on my existing project.
I have cmake_policy(VERSION 2.6) set in my project. Why am I being
pestered by warnings? Shouldn't I get a policy value appropriate for 2.6
(so CMP0043 should be set to OLD)?
CMake Warning (dev) in src/CMakeLists.txt:
Policy CMP0043
I have CMAKE_OSX_SYSROOT defined as something:
set(CMAKE_OSX_SYSROOT
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
CACHE LIST OSX sysroot SDK directory FORCE)
Then later I do a find_library command and it finds a library framework in
It should already support cuda run time building by default. This is what
the OBJ target is for CUDA_WRAP_SRCS. This is what cuda_add_library and
cuda_add_executable do.
On Fri, Apr 18, 2014 at 5:18 AM, Tobias Zirr opensou...@alphanew.netwrote:
Hello,
I just added CUBIN FATBIN compilation
.
Petr
On Wed, Apr 16, 2014 at 9:35 PM, James Bigler jamesbig...@gmail.comwrote:
I see that I can get the value of a variable from a directory using:
get_directory_property(sub1_val1 DIRECTORY sub1 DEFINITION val1)
Can I do the same thing with get_property?
I see a VARIABLE entry, but I
I see that I can get the value of a variable from a directory using:
get_directory_property(sub1_val1 DIRECTORY sub1 DEFINITION val1)
Can I do the same thing with get_property?
I see a VARIABLE entry, but I can't use that with the DIRECTORY indication.
By the way what are the properties on
I noticed in the git history that the kitware robot changed the
documentation in the source files to something with :: characters between
paragraphs.
It also seemed to add them between the paragraphs of the same descriptions:
# CUDA_WRAP_SRCS ( cuda_target format generated_files file0 file1
I already have an implementation for static CUDA runtime linking that I've
been testing in OptiX production builds.
The other one needs some minor cleanups (I commented on it).
On Thu, Jan 16, 2014 at 7:19 AM, Brad King brad.k...@kitware.com wrote:
James,
Please take a look at these
The way I implemented separable compilation it doesn't use nvcc to link.
It relies on the host compiler to do the linking. I'm not sure at first
blush why you are having this problem. One thing that should probably be
done is to change this line of code in FindCUDA.cmake:
# For now we are
When did CMake stop adding /STACK:1000 to the link line?
I just spent several days trying to figure out why my code started failing
in strange ways, and I traced it down to this.
Thanks,
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hmmm... Well that was a not backward compatible way of doing it. This
behavior has existed for a long long time.
Thanks for your help,
James
On Fri, Oct 25, 2013 at 10:58 AM, Nils Gladitz nilsglad...@gmail.comwrote:
On 25.10.2013 18:42, James Bigler wrote:
When did CMake stop adding /STACK
My experience mirrored Clint's. Our version of CMake on the farm was at
2.8.12, but locally developers were at differing versions. What made
matters worse is that it is a lot harder to diagnose problems from farm
built binaries, so it wasn't until one of the 4 developers looking into
this
On Fri, Oct 25, 2013 at 3:28 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 10/25/2013 4:36 PM, James Bigler wrote:
My experience mirrored Clint's. Our version of CMake on the farm was at
2.8.12, but locally developers were at differing versions. What made
matters worse
/ImportedLibrary/CMakeLists.txt
I don't see the second shared library linking to the imported static
library.
On Wed, Oct 16, 2013 at 3:44 PM, James Bigler jamesbig...@gmail.com
wrote:
On Wed, Oct 16, 2013 at 1:34 PM, Giordano Khouri kgiord...@nikon.net
wrote:
The static libraries must be compiled
Is it possible to stop known static libraries from being carried through
shared libraries?
add_library(mystatic1 STATIC ...)
add_library(mystatic2 STATIC ...)
add_library(myshared SHARED ...)
target_link_libraries(myshared mystatic1 mystatic2)
add_executable(myexe)
target_link_libraries(myexe
wrote:
Have you tried using the LINK_PRIVATE signature to target link libraries?
On Wed, Oct 16, 2013 at 2:05 PM, James Bigler jamesbig...@gmail.com
wrote:
Is it possible to stop known static libraries from being carried through
shared libraries?
add_library(mystatic1 STATIC
On Wed, Oct 16, 2013 at 1:34 PM, Giordano Khouri kgiord...@nikon.netwrote:
The static libraries must be compiled with -fvisibility=hidden. Symbols
with default visibility are marked as “public” and will leak from a shared
library. With hidden visibility, they symbols are marked as “private
I have a static library I found using find_library. Typically with shared
libraries I just link against the library and the dependencies come along
for the ride.
What is the prescribed way of doing this for static libraries? I don't
think I want to do create an imported target, as this isn't a
On Tue, Sep 17, 2013 at 11:05 AM, Dan Kegel d...@kegel.com wrote:
On Tue, Sep 17, 2013 at 9:41 AM, James Bigler jamesbig...@gmail.com
wrote:
I have a static library I found using find_library. Typically with
shared
libraries I just link against the library and the dependencies come along
If there is a set(PARENT_SCOPE) why isn't there an unset(PARENT_SCOPE)? It
seems like a hole in the API.
I noticed this when I was trying to update my push_variable/pop_variable
functions. I use set(PARENT_SCOPE) to set the variable outside of the
function, but when doing pop_variable I want to
On Fri, Sep 13, 2013 at 8:21 AM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 05:36 PM, James Bigler wrote:
I discovered a long time ago that VS would link the output of a custom
command.
I just ran local experiments with VS 6, 7.1, 8, and 9 by manually modifying
the ExternalOBJ
I have a couple of issues with this release.
1. file(APPEND ${myfile}
string
string2;
string3)
This generates an error at the ';' character, which never did before. So
far as I understand, a ';' character should still be legal here. Please
correct me if I'm wrong.
2. One of
On Thu, Sep 12, 2013 at 12:10 PM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 01:27 PM, James Bigler wrote:
1. file(APPEND ${myfile}
string
string2;
string3)
This generates an error at the ';' character, which never did before.
So far as I understand
In 2.8.12 and 2.8.11.2 I noticed the following problem for VS 2012 builds.
VS 2010 builds are fine. Also CMake 2.8.10.1 works just fine.
VS 2012 doesn't link the objects into a library. It fails to run the link
command at all. I'm trying to figure out why. I'm comparing the
differences
On Thu, Sep 12, 2013 at 1:32 PM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 03:08 PM, James Bigler wrote:
In 2.8.12 and 2.8.11.2 I noticed the following problem for VS 2012
builds.
VS 2010 builds are fine. Also CMake 2.8.10.1 works just fine.
VS 2012 doesn't link the objects
On Thu, Sep 12, 2013 at 3:07 PM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 04:57 PM, James Bigler wrote:
This seems kind of confusing when the default for all the other VS
generators is to link in the output of the custom command. Does
that not seem like a problem?
The goal
On Thu, Sep 12, 2013 at 3:28 PM, James Bigler jamesbig...@gmail.com wrote:
On Thu, Sep 12, 2013 at 3:07 PM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 04:57 PM, James Bigler wrote:
This seems kind of confusing when the default for all the other VS
generators is to link
On Thu, Sep 12, 2013 at 2:49 PM, Brad King brad.k...@kitware.com wrote:
On 09/12/2013 04:45 PM, James Bigler wrote:
I don't actually add the object file to the build, because VS would
link in the output of the custom command
That's the exact problem the change I linked fixes.
You should
I have a couple of issues with this release.
1. file(APPEND ${myfile}
string
string2;
string3)
This generates an error at the ';' character, which never did before. So
far as I understand, a ';' character should still be legal here. Please
correct me if I'm wrong.
2. One of
I have this same question. There doesn't seem to be a way to have these
imported target see other targets. I can pull the full path out for this
target, but it seems less elegant.
On Thu, Dec 22, 2011 at 11:08 AM, Marco Corvo marco.co...@pd.infn.itwrote:
Hi all,
I have a big project which
On Wed, Jun 12, 2013 at 11:03 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 6/12/2013 10:29 AM, J Decker wrote:
It's not nessesary for 2005, 2008, 2010, or 2012 versions.
visual studio builds a seperate browse information database. 2010 and
12, when in sources you can right click on
Is there a way to use libtool -static instead of ar + ranlib? I'm running
into some situations where ar + ranlib are generating errors where libtool
-static does not.
Basically I have a tool that generates object files (CUDA), but it can only
do so for a single architecture at a time. If I
On Wed, Jun 5, 2013 at 7:45 AM, Stephen Kelly steve...@gmail.com wrote:
James Bigler wrote:
Things get dicey when you want to pass things like include directories as
arguments. There are quotes to deal with as well as maximum argument
length issues. I'm not saying it can't be done
What is this change qt4-macros-TARGET-arg?
Things get dicey when you want to pass things like include directories as
arguments. There are quotes to deal with as well as maximum argument
length issues. I'm not saying it can't be done, but it needs to be done
*carefully*.
I would really really
On Tue, Jun 4, 2013 at 12:06 PM, Brad King brad.k...@kitware.com wrote:
On 06/04/2013 02:01 PM, James Bigler wrote:
What is this change qt4-macros-TARGET-arg?
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ce60ff5
OK, that looks similar to how I would have written it.
I would
code), and I would still be unable to do so with this mechanism. I
guess I might be able to more of that processing into the build time
executed script
On Tue, Jun 4, 2013 at 1:51 PM, Brad King brad.k...@kitware.com wrote:
On 06/04/2013 03:46 PM, James Bigler wrote:
The $TARGET_PROPERTY
Is it possible to create configuration dependent dependencies for custom
commands? I need to specify a different set of dependencies for Debug
versus Release builds in Visual Studio.
Thanks,
James
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Yes. This was an unforeseen side affect when Mac changed the default compiler
mixed with a fix in CMake that changed the default C compiler from gcc to cc
(previously you would get clang's CPP compile and gcc's C compiler).
In general you want CUDA to use the same compiler as the rest of the
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7f19de3c6b559bd3529de46d2017d0a5a2b5cf10
commit 7f19de3c6b559bd3529de46d2017d0a5a2b5cf10
Merge: 533bbb4 b6e9b8f
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Thu Mar 14 12:55:43 2013 -0400
Commit: CMake Topic Stage
I used the following code in 2.8.4, but in 2.8.9 and 2.8.10 it doesn't add
the CUDA_CUDART_LIBRARY library to the eventual link line. I see my target
linking against the parallelprim library but not the cudart library. Did
something change in the interface between 2.8.4 and now?
I'll continue
a test for
IMPORTED_LINK_DEPENDENT_LIBRARIES aside
from trying to create a circular dependency between a single library.
On Wed, Mar 13, 2013 at 4:35 PM, James Bigler jamesbig...@gmail.com wrote:
I used the following code in 2.8.4, but in 2.8.9 and 2.8.10 it doesn't add
the CUDA_CUDART_LIBRARY
is static or shared and works for 2.8.4+.
I'm not sure what the expected behavior is supposed to be, but I attached
my simple reproducer.
On Wed, Mar 13, 2013 at 5:08 PM, James Bigler jamesbig...@gmail.com wrote:
I determined that this failed starting in 2.8.7 (2.8.6 has the cudart
library
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fb71268dbd0e98d7c5d29d7500930e6245352c6d
commit fb71268dbd0e98d7c5d29d7500930e6245352c6d
Merge: db50058 776766f
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Mon Mar 4 15:11:35 2013 -0500
Commit: CMake Topic Stage
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a413ccc433fddff0c1ca0fa6d9cab7f46a3ab55c
commit a413ccc433fddff0c1ca0fa6d9cab7f46a3ab55c
Merge: fb71268 5ab1259
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Mon Mar 4 15:22:53 2013 -0500
Commit: CMake Topic Stage
-
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8965cf74cd40213721aa797f704ea6872ef15958
commit 8965cf74cd40213721aa797f704ea6872ef15958
Merge: 2eb3d64 a790acb
Author: James Bigler jamesbig...@gmail.com
AuthorDate: Mon Mar 4 16:09:01 2013 -0500
Commit: CMake Topic Stage
1 - 100 of 525 matches
Mail list logo
