On 11/18/2015 11:05 AM, Bartosz Kosiorek wrote:
> With this simple patch in attachment I would like to do two things:
Thanks for working on this. Here are some comments on the documentation.
> +This property may be set to a list of files to be placed in the
> corresponding directory (eg.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 20f70b2dcaea62a60cf8fa30d1996ee32e7e3fb5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via d1f4b6b501f477a0ed9af4abadc5995b835b5ba2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 230be56f8a16737754085a2c26ba382c43ff21c9 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 67248baaf98c3c8555dfa85f532c6a840eab10b6 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via b6f471773d943bfb0f5cc012bce3fd25f5f9f7fa (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 7171f64cc108dfb4072def578ef38ed8ce99187b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 5bba0432f4448f5bf3fcc281ce42bc935634ca5d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via 59b6d8a81bc4f975664a1b04cd349235e5a152b7 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via ec649040592ea1ae06b02c3a9665f72f9ffbe6a5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 1ccb417d61e08b69606a9d66b8ae4244f0b051d5 (commit)
via
On Thu, Nov 19, 2015 at 11:04 PM, Tamás Kenéz wrote:
> > set(foobarSRCS foo.c bar.c)
> > set(foobarLIBS ${externalLibFound})
> >
> > which is what the FAQ entry seems to suggest. However, this variable is
> not visible to goo.c. Okay, so as an alternative, I can do this:
>
Dear All,
I am building an application using cmake with external shared library
libLLAPI.so on Ububtu .
I am getting following error:
make -f Source/CMakeFiles/app.dir/build.make Source/CMakeFiles/app.dir/build
make[2]: Entering directory
On 11/20/2015 01:39 PM, Nikita Barawade wrote:
../../../LLAPI/build/Source/libLLAPI.so: undefined reference to
`udev_device_get_devnode'
Before this, while buildinga library libLLAPI.so I got error " fatal
error: libudev.h: No such file or directory" .
It worked fine after installing
> I'd prefer using the PARENT_SCOPE option here...
Jack's initial email continues with "but now the variable is not visible to
baz.c" so using PARENT_SCOPE does not meet his requirements.
> which will make the variables available in the parent CMakeLists.txt.
So does using cache variables.
Hi,
As far as I know this is not possible, but I would love for someone to
point out the CMake invocation I missed. More and more we use a
mixture of languages in projects, such as in VTK where we have Python
wrapping, and tomviz where we have a number of algorithms implemented
in Python (and I
On 11/20/2015 04:43 PM, Marcus D. Hanwell wrote:
I would like to see these files listed in Qt Creator (or insert your
IDE of choice here). Is there anyway to do this, knowing that these
files are not going to be built for a target (or compiled in any way).
Any trick I am missing to make this
On 15/11/15 21:13, digitalriptide wrote:
Did this fix make it into 3.4? After upgrading to 3.4, GCC still seems
to lack -isystem flags on OS X. Is there anything extra I need to do?
It should be fixed for the Makefile and Ninja generators but not Xcode.
My proposed fix broke older Xcode
On Fri, Nov 20, 2015 at 10:46 AM, Nils Gladitz wrote:
> On 11/20/2015 04:43 PM, Marcus D. Hanwell wrote:
>>
>> I would like to see these files listed in Qt Creator (or insert your
>> IDE of choice here). Is there anyway to do this, knowing that these
>> files are not going
On Fri, Nov 20, 2015 at 17:22:33 +, Robert Goulet wrote:
> I'm looking to find where is MSVC_VERSION defined in CMake? I added a
> new platform support that builds in Visual Studio, but MSVC_VERSION is
> not defined for my new platform and I would like to do it just like we
> do for standard
Hello
Could you please give me an feedback regarding that documentation patch?
I have some spare time to fix that.
Because I didn't tested cmake with watchOS and TVos, I wasn't mention about
other than OSX and iOS system.
Once I have such hardware and test it, I will update documentation.
Hello,
I'm using ExternalProject to build libxml2 into a static library, which I
link my application to. I've read a few warnings about combining
ExternalProject with standard CMake targets, but I'm pretty sure this is
the approach I want to take. I do not want to install libxml2 globally
Hi,
I'm looking to find where is MSVC_VERSION defined in CMake? I added a new
platform support that builds in Visual Studio, but MSVC_VERSION is not defined
for my new platform and I would like to do it just like we do for standard
Windows projects. Is it in .cmake files or in .cpp files?
On 11/17/2015 2:46 PM, Jack Stalnaker wrote:
I read about those, but they don't seem to provide a way to add linked
in libraries, so it didn't seem to add a lot over a list of sources. In
autotools, you could bind your convenience lib with any dependencies via
a LIBADD primary, and the added
On 19/11/2015 16:15, Brad King wrote:
On 11/18/2015 12:07 PM, rle...@codelibre.net wrote:
Patch attached to add imported target (XercesC::XercesC),
along with a unit test.
Looks good, but please also update the module documentation.
We'll also need a release note, e.g.
$ cat
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20151120)
+set(CMake_VERSION_PATCH 20151121)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
26 matches
Mail list logo