I'm preparing to install PCL (Point Cloud Library), and their building
PCL's dependencies from source tutorial says to download Cmake. However,
in the Cmake read me it says,
"If you don't have any previous version of CMake already installed
I'm putting together an NSIS installer for my project on Windows. It works
fine for Static installs, but shared library installs don't work because the
binary is in the bin directory and the libraries are in the lib directory. I
would know how to fix this on Linux, but am a bit at a loss on Wi
Thank you, it works now and that is definitely a better work around.
-Kris
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Thursday, June 13, 2013 5:01 PM
To: Malfettone, Kris
Cc: cmake@cmake.org; Mike
Subject: Re: [CMake] Generator Toolset fails
On 6/13/2013 4:36
On 6/13/2013 4:36 PM, Malfettone, Kris wrote:
> Just wanted to add some extra information. I found a way to work around
> the problem by first generating with:
> cmake –G "Visual Studio 11"
>
> Then reconfiguring directly after with:
> cmake –G "Visual Studio 11" -DCMAKE_GENERATOR_TOOLSET=v100
Just wanted to add some extra information. I found a way to work around the
problem by first generating with:
cmake –G "Visual Studio 11"
Then reconfiguring directly after with:
cmake –G "Visual Studio 11" -DCMAKE_GENERATOR_TOOLSET=v100
I think the key to the workaround working is that while
I have this same problem but didn’t see a response to this problem. Is there a
fix for it? Or information related to it?
-Kris
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Mike
Sent: Wednesday, May 29, 2013 10:06 AM
To: cmake@cmake.org
Subject: [CMake] Generator
Hi,
I'm currently converting some cross platform projects to CMake, for easier
maintainance in the future.
They use some third party libraries, which it's easier for me to NOT
convert to CMake (because then I have to update that when the third party
changes their projects), these are built using
Sorry, David Cole pointed out that I miswrote (and have very poor english to
begin with). Sorry. What I meant to say was that we put the generated cmake
files in the _source_ tree. Text in full:
As a counter example (which perhaps could be improved on), we are currently
putting our generated cm
As a counter example (which perhaps could be improved on), we are currently
putting our generated cmake files in the build tree. The reason for this to
allow git post-checkout and post-rewrite hooks to updating the build files if
needed. We have python script that rewrites the files if they wou
It's nice when everyone agrees.
thanks
On Wed, Jun 12, 2013 at 2:49 PM, Matthew Woehlke <
matthew.woeh...@kitware.com> wrote:
> On 2013-06-12 15:30, William McKenzie wrote:
>
>> Just wondering what the common convention is here. If I have some
>> generated
>> c/c++ source files, say from gSoap
10 matches
Mail list logo
