With CUDA 8.0 and 9.0 installed and Visual Stuido 2013 (and god only knows
what versions of 2017 updated up grades with whatever tools versions)
CMake -> Visual Studio 12 2013 Win64 -> Optional toolset to use (arguments
to -T -> cuda=8.0
The CXX compiler identification is MSVC 18.0.31101.0
The
> > Can't that be set by passing the toolset with a -T
>
> That is what I was trying to say with my last sentence. You will need
> to use CMake 3.12 to have support for specifying the minor toolset
> version though.
>
> >>>
> >>> The MSVC / CUDA support recently has been very challenging to kee
On Wed, Aug 15, 2018 at 11:58 AM, Robert Maynard wrote:
> The MSVC / CUDA support recently has been very challenging to keep track
> of. In general CUDA will only support a single patch release of MSVC, and
> given how MSVC 2017 doesn't easily allow rollbacks and has a pretty
> aggressive update
etecting CXX compile features - done
CMake Error at CMakeLists.txt:14 (PROJECT):
No CMAKE_CUDA_COMPILER could be found.
Ditto for that attempt
Aces! This sure is awesome.
On Wed, Aug 15, 2018 at 10:45 AM, Brian Davis wrote:
> Yes I know all about the bit about having to reinstall CUDA (been us
ad 2013 after being told to generate Visual Studio
> 2013 project files.
>
> As Hendrik stated CMake defers to the windows shell/explorer for
> opening solution files.
> On Tue, Aug 14, 2018 at 7:27 PM Brian Davis wrote:
> >
> >
> > It also cannot find CUDA likely
It also cannot find CUDA likely as CUDA was not installed after 2017. I
would like it to load 2013 after being told to generate Visual Studio 2013
project files. Is this difficult to ask fo Kitware? I am sure there are
certainly some shenanigans like path or VS2017 hooking calls to 2013 tools
or
Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing
2017... sigh.
Without even regenerating or re configuring (even though that has no effect
either) when "Open Project" is selected 2017 is opened and not 2013... errr
what am I targeting again? Happened after 2017 install. How
The answer to what parameters can be specified the "whitelist" as it is
refereed to is documented (thanks to Raul's help):
https://cmake.org/cmake/help/v3.9/command/add_library.html?highlight=interface_#interface-libraries
with these key bits:
"Details about the imported library are specified by
Is the goal of add_library interface libraries to add the concept of
inherited build properties not dependent on the directory project
inheritance structure of CMake?
This is to say attach any and all cmake properties, flags, etc to a "dummy"
target that can then be used by other target to "inheri
On Thu, Aug 24, 2017 at 2:46 AM, Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com> wrote:
>
> Ok got it sorry to hear that certainly because, as soon as I hear
>> something that would be useful somehow I end up needing it the next day.
>> So sorry for us both.
>>
>> From what your are saying
Y CXX_STANDARD 14)
> set_property(TARGET blah PROPERTY INSTALL_RPATH "@loader_path/whatever")
>
>
>
>
> ---
> Jean-Michaël Celerier
> http://www.jcelerier.name
>
> On Wed, Aug 23, 2017 at 11:23 PM, Brian Davis wrote:
>
>> So there is some odd replies in the cma
So there is some odd replies in the cmake mailing list possibly
responses to wrong message, but this looked like a response to mine
even if the initial reply to bit is not right from Nicholas. Anywho
here goes:
@Jean-Michaël Celerier
-- snip --
>* - Says that custom functions such as add_{projec
On Wed, Aug 23, 2017 at 2:07 AM, Clément Gregoire wrote:
> I can't argue too much why paths or absolute on cmake as I don't know the
> rationale behind it is. While your point about command line limit makes
> sense, I feel like a system limiting command line size to this extent is
> dumb if it do
On Tue, Aug 22, 2017 at 12:42 PM, Clément Gregoire wrote:
> No you're not meant to specify paths yourself, you should just use
> find_library.
> Check how modules such as FindTIFF.cmake are implemented.
>
Please doc in CMake all the things I am "meant to" so as I can live inside
that happy littl
and provide future
target_link_directories(
targ
INTERFACE
debug ${TOP}/build/x64/Debug/Libraries/
optimized ${TOP}/build/x64/Release/Libraries/
)
with debug / optimized / general capability
then targets could support multiple debug / release dirs even if CMake
(CMAKE_INSTALL_PREFIX
Upon further reflection the abs paths for every lib is absolutely not
defensible.
1) Pass only the short lib name to target_link_libraries
2) Add absolute path to future target_link_directories if you must
Then it's one (1) long path on the command line string and not N long paths
fore each lib
50)."
"Please move the ITK source code directory to a directory with a
shorter path."
)
endif()
Sadly no and .. ok so it's 50.
-- snip --
I would certainly like to hear a defense of this "logic". I like to say
that I discourage insanity.
On Mon,
Why does:
Interface Libraries
https://cmake.org/cmake/help/latest/command/add_library.html?highlight=add_library#id3
allow include directories via
target_include_directories(INTERFACE)
but not link_directories
https://cmake.org/cmake/help/latest/prop_dir/LINK_DIRECTORIES.html?highlight=link_di
Now that I have working machines and can create CUDA app (simple)
successfully that will run
While trying:
message( "GPU_ARCH = ${GPU_ARCH}" )
target_compile_options(
${SOME_LIB_NAME}
PRIVATE
$<$:${GPU_ARCH}>
)
with output of:
GPU_ARCH = -gencode arch=compute_30,code="sm_30,compu
On Tue, Aug 8, 2017 at 2:31 PM, Lectem wrote:
> I think that you are looking for the toolchain files :
>
> https://cmake.org/cmake/help/v3.0/manual/cmake-toolchains.7.html
>
>
>
> The other option is to use a cmake script to specify your variables which
> includes CMakelists.txt (or the other way
tation!
Thanks for the heads up on the feature. Nice!
On Wed, Aug 9, 2017 at 5:20 AM, Cristian Adam
wrote:
>
>
> On Tue, Aug 8, 2017 at 8:08 PM, Brian Davis wrote:
>
>>
>> Is there a CMake equivalent to a site-config.jam or user-config.jam
>>
>> http://www.boos
I am so lost in CMB0054 errors I and internet searches I can't remember why
I wanted Itk-4.8 in the first place. Here goes:
When using CMake 3.9.0-rc6 or basically 3.1+ (onward) and trying:
find_package( ITK )
with 4.8 built / installed and receiving:
CMake Warning (dev) at install/lib
Is there a CMake equivalent to a site-config.jam or user-config.jam
http://www.boost.org/build/doc/html/bbv2/recipies/site-config.html
basically a CMake file the user can put in a project directory that CMake
will read first when using cmake-gui that allows user to specify stuff they
don't want t
Upon:
wiping Dell 7559 (yes the weirdness has gotten this bad), reinstalling from
Dell Factory image
upgrading system to Latest Win 10 (now not in developer mode anymore)
Dell update to get latest drivers and other goobly bits
Removing all Virus Scanners to keep this from possibly interfering
Inst
Can someone explain to me the meaning of the statement at:
https://cmake.org/cmake/help/latest/release/3.8.html?highlight=cuda
Make learned to support CUDA as a first-class language that can be enabled
via the project() and enable_language() commands.
CUDA is currently supported by the Makefile
Reading:
https://cmake.org/cmake/help/latest/release/3.8.html?highlight=cuda
Can someone explain to me how CUDA is now supported as a first class
language,
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offe
In latest CMake Doc for cmake modules at:
https://cmake.org/cmake/help/v3.0/module/CMakePackageConfigHelpers.html#module:CMakePackageConfigHelpers
I find:
Example using both configure_package_config_file() and
write_basic_package_version_file(): CMakeLists.txt:
set(INCLUDE_INSTALL_DIR include/
crickets crickets... crickets...
That's the response I get from the internet?
Here are some other interesting bits:
https://cmake.org/cmake/help/v3.8/manual/cmake-packages.7.html
Does not make any reference to
configure_package_config_file
in
https://cmake.org/cmake/help/v3.8/module/CMak
Apologies for not responding sooner... this fell off my radar and I found
it in my email.
On Thu, Jan 12, 2017 at 6:29 AM, David Cole wrote:
> Why not just use a BUILD_COMMAND which builds the VS project using the
> msbuild command line directly?
Do you have an example of this?
Even if this i
Thanks Brad for replying. Comments below.
On Wed, Jan 22, 2014 at 11:09 AM, Brad King wrote:
> On 01/22/2014 11:27 AM, Brian Davis wrote:
> >
> http://cmake.org/gitweb?p=cmake.git;a=blob;f=Help/manual/cmake-language.7.rst;hb=1b395813#l393
> >
> > This document does not
Continuing on here from results of bug submittal at
http://public.kitware.com/Bug/view.php?id=14705 I will try to post whatever
necessary bits from that here in hopes of making this cohesive discussion.
The bug report example has two CMakeLists.txt files:
external_project/CMakeLists.txt
referred
Lets say you download a swanky open source project off the web and hook it
into your project using he superbuild and externalproject_add. You write
some code that uses said OSS project and you get the error in visual studio
2012.
Error52error LNK2038: mismatch detected for 'RuntimeLibrary
Thanks for the response on this, I was able to get this to work (to
degrees) with libtiff and Jasper as well as other non CMake-a-fied
projects. I have run into another issue where I wish to use configure_file
to generate a CMakeLists.txt file in the directory where
ExternalProject_add dumps the s
> I guess at the end of the day what you are talking about is a static code
analysis tool for the CMake language. Those tools look at all possible
branches of code and try to detect errors.
What I would like to see at a minimum is a CMake Debugger showing a window
with the list of variables, not
I also get:
2> nvcc Hâ∞(Ç=y░: nvcc cannot find a supported cl version. Only MSVC 8.0
and MSVC 9.0 are supported
2> CMake Error at
CMakeFiles/gpuReconPlugin_generated_gpuPMatrixRecon.cu.obj.cmake:194
(message):
2>Error generating
2>
C:/Users/bdavis5/Documents/QS/QS-NIH/source/branches/trunk/
I recently had to upgrade to vs 2010 to use NSight debugger for NVIDIA GPU
degging and was using 2.8.0. This version would load all but my CUDA
related projects the cpuReconPlugin and the gpuReconPlugin. These two libs
are defined in the same directory and share common source (which has been
prob
I'll give COMPILE_FLAGS another try. There is always a chance with how I
was using it that it had no effect or a bug/typo in my usage..
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensou
I am posting this back to cmake so others can follow along. I too use gmail
and often forget the reply all.
On Thu, Aug 19, 2010 at 9:11 PM, Clifford Yapp wrote:
> Um... if you mean "CMakeified" in the sense of them having CMake files
> for building, no... my understanding was that you don't re
>
>
> We override the standard CMAKE__FLAGS (C CXX Fortran) and use it as a
> baseline. Then, for individual source files it is possible to override them
> in a separate file using:
>
>
Yes this is seemingly common practice in CMake land. The problem with this
approach is when using add_subdirecto
CMAKE_CXX_FLAGS..., CMAKE_C_FLAGS... and CMAKE_C_STANDARD_LIBRARIES_INIT and
friends are seemingly global variables. Is there a way to override (all of)
these on a per target basis? A method which is not tied to the directory
(properties). One that does not simply append such as COMPILE_FLAGS, bu
> You are getting the correct output. Look at the flags and target files
> more closely:
>
Yes I know it is working. It was working in the prior email where I
exclaimed "Yippie". I was just wondering if there was anything else I
should be aware of and I was not sure if I was clear in conveying
>> I just noticed your email in my FindCUDA filter from the CMake list. I'm
not sure why it didn't show up sooner.
No worries. I let this thread die for a while while I worked on other
things. I was back recently trying to fix this issue as I now want to
compare the cpu/gpu recons separately. I
One more thing for thoes interested DEFINITIONS_STRING is set in the
following manner:
--snip--
set( DEFINITIONS_STRING )
foreach( DEFINE_STR ${ARG_DEFINES} )
set( DEFINITIONS_STRING ${DEFINITIONS_STRING} -D${DEFINE_STR} )
endforeach()
--end snip--
James I was going to cc you on my latest findings. Thanks for giving me a
"way out" with out having to patch the FindCUDA. I recently came to the
same conclusion as your recent post.
1. CUDA_ATTACH_VS_BUILD_RULE_TO_
CUDA_FILE can really only cause problems with parallel builds. Are you
performi
>From my current research into this problem it looks like the issue can be
traced to these lines in FindCuda.cmake
--snip--
# Get the list of definitions from the directory property
get_directory_property(CUDA_NVCC_DEFINITIONS COMPILE_DEFINITIONS)
message( "CUDA_NVCC_DEFINITIONS = ${CUDA_NVCC
First off, I don't know the answer to your question, but I am curious how
you are getting CMake to create inherited projects. What are the commands
you are suing to create an inherited project in CMake? This is something I
think I can use in my projects.
__
>
> --snip--
>
> Ah you're on windows, make sure that you deselect the option to
> associate the build rule with cu files as this does the wrong thing
> when you're compiling the same file multiple times with different
> defines.
> --end snip--
>
> Can you give me more info on this? I have looked
>> Well, I don't think there's a way around it. But you can use a loop to do
it:
Ok good to know.
>> Another thing, though: Never, ever, configure a file into the source
tree. Doing so is a recipe for disaster...
Curious as to why.
This is exactly what I am doing so I can run matlab among other
I am using configure_file to generate a batch file on the fly with CMake
based on location of Libs found (adding to PATH env var in batch script) and
I was wondering if there is a way to not have to create a lot of variables
for native paths such as below
--snip CMakelists.txt --
SET( GTK2_ROOT_DI
I think Ryan's comments help support my assessment of FindWhatevers. Add
recently downloaded GTK in GLade 3.6 for windows and can now add this to
list of not working FindWhatevers. find_package( GTK2 ) of course does not
work for this as of today.
Statements like
"CAUTION: The contents of this
Fails miserably on Win32 (XP), Win7 64, Win Server 2008 64 too. You'll find
as I have that the "find whatevers" are not all that they are cracked up to
be. CUDA is another example. find_package should really be named
attempt_to_find_package_and_when_you_can't_simply_tell_me_the_vars_to_set(
pack
>
>
> I'm doing something similar, but I hit a problem when adding the
> dependencies
> so that the external projects are actually built.
> The issues is that it is currently not possible to use add_dependencies()
> with
> imported targets, here's the issue for it:
> http://public.kitware.com/Bug/v
I would recommend using EXTERNALPROJECT_ADD.
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#module:ExternalProject.
Though I am not building in ITK as of yet I am using VTKEdge which depends
on VTK
--snip vtkedge_config.cmake --
macro( vtkedge_config )
set( VTK_EDGE_PACKAGE VTKEdge-5-4-0
Can a roadmap be posted for CMake? Such as is for other projects at:
http://www.cmake.org/Bug/roadmap_page.php
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep me
--snip--
I'm using Boost and I've never hard to work with special defines and
compile flags. That's the power of proper automatic support.
--end snip--
That's the power of Boost. These guys have really figured it out. I too
would like to see some of the Boost.Build concepts make their way into
C
--snip--
Because if they were excluded, we would have someone on the list next
month asking why she can't create empty directories with install()
commands.
--end snip--
True point taken. Then we would have 2 people who are correct ... Olaf and
this said hypothetic other person. With software th
>>>True, but note the "*.h" filter. After the filter, the dir is empty,
so it doesn't make any sense to create it at install time.
Yep I tried it and as you say .svn appears even though the "filter" should
grab .h files
So I echo Olafs's question why is .svn dir grabed when .h filter should be
en
>> It does, but should not be necessary. Why aren't empty dirs excluded by
default?
svn directory is not empty.. it is hidden, but not empty... at least it
shouldn't be if the svn is working correctly. I am probably missing
something here and should give this a try myself as I currently am using
You could switch to git :-) so there are not all these .svn dirs splatted
all over the tree... One of the many things I hate about svn and love about
git. But in all seriousness try using the PATTERN "svn" EXCLUDE. I have
not used this, let me know if it works.
install(DIRECTORY icons scripts/
>
> Good idea but this seems difficult to do.
> In Olaf case it may be doable to spit out a better error message
> explicitely
> saying that "T" was considered as the "" argument of PROJECT,
> because PROJECT is a builtin
>
> I was just agreeing with Olaf and stating a issue I ran into on error
rep
I agree with Olaf. CMake needs better error reporting for parameter
checking on macros and functions
I ran into similar with use of:
http://www.cmake.org/Wiki/CMakeMacroParseArguments
where I elided the empty quotes "" and it was as though the macro/function
it was contained in did not exist as
I too would like the answer to this and other questions. I have been having
the same problem with CMake (among others)
How to build a project that contains multiple 3rd party sources where:
1) build of one package is dependent on the not yet installed install of a
dependency package where the in
--snip--
Ah you're on windows, make sure that you deselect the option to
associate the build rule with cu files as this does the wrong thing
when you're compiling the same file multiple times with different
defines.
--end snip--
Can you give me more info on this? I have looked in CMake variables
> Shouldn't this be COMPILE_FLAGS?
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_dir:COMPILE_DEFINITIONS
Under properties on directories
Preprocessor definitions for compiling a directory's sources.
The COMPILE_DEFINITIONS property may be set to a semicolon-separated list of
processor
Also strange is I have to change the code:
-snip-
#ifdef gpuPMatrixRecon_EXPORTS
#define DllImportExport __declspec( dllexport )
#else
#define DllImportExport __declspec( dllimport )
#endif
-end snip-
to
-snip-
#if defined(gpuPMatrixRecon_EXPORTS) || defined(cpuPMatrixRecon_EXPORTS)
#define
>> Try changing your macro into a function instead.
I did try as you suggest and it works exactly the same as if it were a
macro.
>From my cmake gui output debug messages the macro or function is seeing the
CPU_RECON and GPU_RECON.
ARG_SRCDIRS =
ARG_CPP_SOURCES = gpuPMatrixRecon.cpp;CUDADeviceP
In regards to this topic *in my opinion* linking directory structure/level
to CMake CFLAGS is not a good design (on the part of CMake)... again *in my
opinion*.
I would prefer there was project level (and ability to inherit project level
settings from another project using the project() where proj
-snip-
I do not think that this is necessary. CMake should overwrite the according
values.
-end snip-
IMHO clearing the cache and starting from scratch is the best approach if
you are developing the build spec and not simply compiling 3rdParty source
as the CACHE may contain variables you created
I have a macro which gets called to create cuda and matlab mex enabled
libraries and apps. I call this macro **twice from within a single
directory** to create 2 libraries. Problem is that I desire to set compiler
defines -DWHATEVER=goop etc differently for each lib (for each of the two in
questi
>> Is there also a way to disable recursive sub directory project
inheritance
>> in CMake?
>I don't know what you mean by "project inheritance", but AFAIK it is not
>possible to disable inheriting settings from your parent directory.
In Microsoft VS land this would be:
Inherited Project Property S
Performing
grep -R "[Cc][:][\]" * > AbsolutePathProb.txt
on my build dir created by CMake and looking at the output saddens me :-(
Brian
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/open
I noticed that if I have a buried CMakeLists.txt file which contains the
following
file(GLOB_RECURSE DICOM_TEST_SERVER_SRC src *.cpp )
and
INCLUDE_DIRECTORIES(
include
)
Where src contains cpp files and include contains include files CMake uses
absolute paths for include path, but relative
So I have various CMakeLists.txt files in my directory structure. Some with
the PROJECT( name ) specified at the top and some without. I am using
add_sub directory to add each directory.
/CMakeLists.txt
/source/cpp/app/CMakeLists.txt
/source/cpp/app/someapp/CMakeLists.txt
/source/cpp/lib/CmakeLi
Here is the latest which includes wroking build of dcmtk NOTE the additon of
-DINSTALL_PREFIX=${INSTALL_PREFIX} as dcmtk required this move its install
eventhought CMAKE_INSTALL_PREFIX was specified. Boost is still not building
as boost wave and serialization do not build, but hey I guess 82 out o
ExternalProject_Add does not like BINARY_DIR same for multiple packages...
Why?
SET( THIRD_PARTY_PACKAGES
vtk-5.4.2
dcmtk-3.5.4
boost-cmake-1_41_0
)
foreach( PACKAGE in ${THIRD_PARTY_PACKAGES} )
ExternalProject_Add(
${PACKAGE}
DOWNLOAD_COMMAND ""
SOURCE_DI
Update: currently crying uncle ... and switching to ExternalProject_Add.
CMake and the third party libs were simply not designed for this.
Question on ExternalProject_Add above:
ExternalProject_Add(
DOWNLOAD_COMMAND ""
CMAKE_ARGS
-DMYPROJ_UBERBUILD:BOOL=OFF
SOURCE_DIR ${CMAKE_CURRENT_SO
The -m64 seems to be a buried unaccessable option due to nvcc_flags variable
within cmake-2.8.0-win32-x86/share/cmake-2.8/Modules/FindCUDA.cmake which
generates my nbody_generated_bodysystemcuda.cu.obj.cmake file. If I try the
wack-a-mole approach:
SET( nvcc_flags "" CACHE STRING "" FORCE )
a w
Good question.
sadly http://www.cmake.org/Bug/roadmap_page.php does not include cmake.
Brian
On Fri, Jan 22, 2010 at 9:17 AM, Tim St. Clair wrote:
> When is the planned release of 2.8.1?
> Is there a online roadmap?
>
> --
> Cheers,
> Timothy St. Clair
>
__
I have overcome the issues with MSVCR90D.dll and MSVCP90d.dll by installing
Visual Studio 9 SP1. Which seems to fix references to amd64 dlls. Why this
is not in the web update is anyone's guess. Just more MS super spectacular
awesomeness.
Now on to my latest (CMAKE) problem. I can build and ru
>
>
> What kind of errors were you getting?
>
>
I would point to a URL on GMane for the thread titled "Build only what you
need in third party libs" , but it looks as though Gmane does not have all
the postings. I was getting bounces back from CMake mailing list due to
size of email.
Here is an e
On Tue, Jan 5, 2010 at 12:23 PM, James Bigler wrote:
>
>
>> I ask my self two questions:
>>
>> 1) Why is CUDA_NVCC_FLAGS not set to some default build setting that would
>> just work out of the box? - I get the answer to this question when I turn on
>> CUDA_VERBOSE_BUILD_MODE - It is being set un
So I figured out the answer to:
Can anyone point me on a path which would help me figure out what (global
project settings) in dcmtk could be causing these kinds of changes in my
unrelated nbody project?
I removed (i.e. the force to use earlier version):
# check required version of CMake
CMAKE_M
Part 1 - Being resent in brokendown form due to 40kb limit on mail list
Continuing on with my attempt to build a project with includes 3rdParty Libs
I have run into a problem when adding library (using add_subdirectory(
pathtowherever/dcmtk dcmtk ) dcmtk (Dicom Toolkit) and building a CUDA test
ap
Part 2 - continued from above
Now finding where allocateNBodyArrays is in the files should not be hard,
but then again I am suing Win7. On a REAL os I would use grep. In the
search bar in Win7 I type in allocateNBodyArrays and search NVIDIA SDK and I
wait for Win7 to allow me to select find in
Part I - This original post bounced off CMake mail list due to 40kb limit.
I am was attempting to build the nbody source in the CUDA sdk to both learn
CMake and CUDA build settings (this is a documentation of that experience -
heck maybe this will help someone else). After moving the sources into
>
> There are a block of these in tools/build/CMake/BoostConfig.cmake, feel
> free to delete them. They were added a long ago, before anybody had
> thought that one might try to build boost in a subdirectory like this.
> Here again boost.cmake is being strange and difficult due to its (imv
> misg
> > There will never be an easy way to pull external projects directly into a
>> > calling project because the external things are not even guaranteed to
>> be on
>> > disk yet at configure time of said calling project.
>>
>>
>> Yeah, kind of a chicken-egg problem...
>>
>
> Exactly. That's why we
> You are correct: projects that are all intermingled together with
> add_subdirectory calls in a parent project *can* interfere with each other,
> especially if they do anything with "FORCE" and change variables to
> "INTERNAL" to hide them from developers. And then there can simply be
> uninte
I am continuing my attempt (latest in the saga) to use cmake to build 3rd
third party libraries and integrate my code and hopefully build only what I
need.
The two libraries I am building currently are dcmtk (DICOM library) and
boost.
I am trying to use cmake to create a project which includes d
See below
On Mon, Dec 7, 2009 at 1:26 PM, troy d. straszheim wrote:
> Michael Jackson wrote:
>
>>
>>
>> On Dec 7, 2009, at 1:28 PM, troy d. straszheim wrote:
>>
>> Michael Jackson wrote:
>>>
So you are wanting to include the Boost sources in your project and you
just want to build a sp
it a shot and see what happens.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Sat, Dec 5, 2009 at 4:15 PM, Brian Davis wrote:
>
> I have used boost jam befo
I have used boost jam before and there was a mechanism to build only what
you need by specifying dependencies within the boost libraries. bjam would
then run off calculate deps and build only what I needed. In CMake is there
such a feature to specify a third party library and specify only the targ
, 2009 at 10:31 AM, Tyler Roscoe wrote:
> On Fri, Dec 04, 2009 at 09:04:45AM -0600, Brian Davis wrote:
> > What I would like to see is:
> >
> > PathToWherever/Debug/bin
> > PathToWherever/Debug/lib
> > PathToWherever/Debug/cfg
> > ...
> >
> > PathTo
I was wondering if there is now a cleaner implementation of the following
issue (see prior attached email below from Philip) where the PREFIX HACK
must be used to remove Debug and Release from the ouput path.
What I would like to see is:
PathToWherever/Debug/bin
PathToWherever/Debug/lib
PathToWh
extension is .gz
So TAR_EXT and GZ_EXT can be tested for and zxvf or xvf can then be used
appropriately amd TAR_OPTS set accordingly.
Thanks,
Brian
On Wed, Nov 25, 2009 at 3:24 PM, Eric Noulard wrote:
> 2009/11/25 Brian Davis :
> >
> > for a given file of the form:
> >
> &g
for a given file of the form:
openssl-0.9.8a.tar.gz
I call as an example:
get_filename_component( TAR_EXT openssl-0.9.8a.tar.gz EXT )
and I get for TAR_EXT
.9.1.tar.gz
Which is not quite what I was expecting.
I was expecting .gz and with successive calls I would get .tar
Is there a mechan
So I found this thread below and tried the command at the promp (Win7):
cmake -E tar xvf
CMake Error: Problem with tar_open(): No such file or directory
CMake Error: Problem extracting tar: ${TARDIR}/mytar.tar
cmake -E tar xvf openssl-0.9.8a.tar
CMake Error: Problem with tar_open(): No such fil
97 matches
Mail list logo
