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 c29302b3f3ff6ca0822afe0a19c66bad12542ac9 (commit)
via
Hi Yi-Hong,
I think that this is an issue that was recently fix in CMake which is not in
our fork. I’ll look at pulling in this change in our branch.
From: Yi-Hong Lyu [mailto:b95705...@ntu.edu.tw]
Sent: Wednesday, February 3, 2016 11:46
To: Gilles Khouzam
Cc:
On 4 February 2016 at 04:45, Adam Rankin wrote:
> Hello all,
>
>
>
> I am trying to sort out a project with multiple layers of dependencies and
> I am trying to figure out the “right” way of configuring things.
>
>
>
> First easy question: Should a value xyz_LIBRARIES contain
Dear Brad,
thanks for your advice. An accoring patch is attached.
> There is no reason to have negative values for that, so please update
> both cmLinkInterface::Multiplicity and cmGeneratorTarget::Multiplicity
> to use `unsigned int` and follow through with any further changes
> needed for that
On Wednesday, February 03, 2016 13:08:42 Andrew Bell wrote:
> If my package is installed to a non-standard location, my
> Config.cmake file is currently also installed to the non-standard
> location and can't be found by dependent projects.
>
> I see that there's export(PACKAGE ), but this
Meet the fresh update online installers (CMake3.5.3.5.20160203):
http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe
and
http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe
If you have used them previously, then just update via "CMake Maintenance Tool".
These installers were
On 02/03/2016 02:31 PM, Brad King wrote:
> install: Add EXCLUDE_FROM_ALL option (#14921)
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0b6c4729
>
> Tests: Add cases for install() command EXCLUDE_FROM_ALL option
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=670fa897
I've had
Ok, that makes sense to me. What I’m seeing though, is that find modules and
xyzConfig files for some software packages do not make a variable available
that contains just target names. Xyz_LIBRARIES contains full path file
locations.
This is my immediate frustration with leptonica for
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15952
==
Reported By:Chaoren Lin
Assigned To:
A selfish request: would it be possible to slip this into the 3.5
release? This is something that I (and the company I work for) are
very interested in, and I would like to avoid pulling a fork into our
workstream.
Cheers,
Steve
On Mon, Feb 1, 2016 at 8:47 AM, Gilles Khouzam
I downloaded cmake 3.5.0-rc1 to try it out.
The Windows installation doesn’t appear to provide all the required
dependencies. ‘cmake-gui’ will not launch and provides the error
“Qt5Widgets.dll is missing form your computer.” Do I need to install a specific
Qt runtime before installing cmake
Hi Nicolas.
Last time I asked for something like that, it was rejected:
http://public.kitware.com/Bug/view.php?id=13020
But maybe the stance could change on that? After all, I don't think CMake
would want to cater for every possible postprocessing anyone needs. Perhaps
it could be considered if
Hi Yi-Hong,
I’ve updated our branch to include the fix to not require the Windows 10 SDK.
But I think that I misunderstood what you had meant by Clang-CL.
The support I added was for Clang with the Microsoft CodeGen engine which is
included in Visual Studio 2015 Update 1, what’s where the
_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160203)
+set(CMake_VERSION_PATCH 20160204)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hi Vadtec.
*The* standard CMake way of dealing with building your dependencies is the
ExternalProject module (
https://cmake.org/cmake/help/latest/module/ExternalProject.html ). It's a
huge beast, but I belive there are some examples and tutorials available
out there.
The gist is: you create a
Hello all,
I am exploring FindZLIB.cmake and FindPNG.cmake and they both use
SelectLibraryConfigurations.cmake. The macro in this file populates
xyz_LIBRARIES with library file locations.
I am wondering if it should not be populating _LIBRARIES variable with target
names? Can it even possibly
On 02/03/2016 12:47 PM, Adam Rankin wrote:
> I am wondering if it should not be populating _LIBRARIES variable
> with target names?
The _LIBRARIES variables are essentially the legacy interface to
modules that provide imported targets. Clients should choose to
use the imported targets
Ok, I admit I'm just diving into cmake internals so I'm still catching up.
Is there documentation on best practices for writing findxyz modules?
How does a client determine the target names that are imported after calling
find_package?
Thanks for the help, I'm happy to do my learning by
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 1d96c624590700cbc8a6997e6149da5d2bca3a86 (commit)
via
Hello all,
I am trying to sort out a project with multiple layers of dependencies and I am
trying to figure out the "right" way of configuring things.
First easy question: Should a value xyz_LIBRARIES contain target names, or
library file locations?
Second question: Should a FindXYZ.cmake
Hi,
I have been able to replicate the problem with the Windows installer
not properly installing the Qt libraries. I have tested the Linux
x86_64 binaries on a Ubuntu 12.04 machine and everything works, but I
will locate a RHEL machine and see if I can replicate your issue.
On Wed, Feb 3, 2016
The window for new CMake 3.5 features is closed now that we have
started the release cycle.
On Wed, Feb 3, 2016 at 12:42 AM, Roman Wüger wrote:
> @Brad, @Clinton: Could we add this feature into CMake 3.5.0, because on
> newer Mac OS systems the package maker is already
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 47bd1c7197d01ebca3239efc4223db2082be2340 (commit)
via
On 02/01/2016 05:01 AM, Nick Lewis wrote:
> https://cmake.org/Bug/view.php?id=14921
Thanks. Actually my request in the issue tracker to post here was meant
to have the actual patch file attached so people can see it without
digging through the messages and attachments there. Patch revisions
or
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 72a585d3534616b0cf4b241d3b6eeb50f44da79a (commit)
via
Ah, gotcha.
So, is it expected that each project in a client's package will call
find_package(xyz)?
I am used to the top level CMakeLists finding all the dependencies, and then
passing the information down into projects. I am happy to update our system
behavior to match what is more correct.
Hello Gilles,
Here it is:
PS > cmake -G "Visual Studio 14 2015" -T v140_clang_3_7
-DLLVM_PATH="E:\\llvm" -DCMAKE_SYSTEM_VERSION=8.1
-DCMAKE_C_COMPILER="E:\\e2tools\\ext-tools\\llvm\\clang-cl.exe"
-DCMAKE_CXX_COMPILER="E:\\e2tools\\ext-tools\\llvm\\clang-cl.exe" ..\src\
-- The CXX compiler
I'm working on a reproducer. For now, all I can say is that it looks like the
segmentation fault occurs on this command:
install( EXPORT foo-targets
DESTINATION foo
EXPORT_LINK_INTERFACE_LIBRARIES )
-kt
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent:
If my package is installed to a non-standard location, my
Config.cmake file is currently also installed to the non-standard
location and can't be found by dependent projects.
I see that there's export(PACKAGE ), but this creates an entry in
the registry for the build location of the PROJECT
Hello Gilles,
Thanks for you mail. It is really useful to me but I encounter an error. My
use case is to use clang-cl with my own target instead of x86/x64 target.
Therefore I don't want to include any headers of VS x86/x64 and use any
library of VS x86/x64:
PS > cmake -G "Visual Studio 14 2015"
Thanks Domen! The use of original-case for in
CPACK_RPM__ was indeed the problem. I never did get the
CPACK_RPM_*_PACKAGE_PREFIX variable to work but I'm using a different
(probably more correct) approach that gets me what I wanted.
Can this use of mixed case-sensitive/all-upper-case can be
On 02/03/2016 11:19 AM, Thompson, KT wrote:
> On RHEL 6.7, I extracted the prebuilt x86_64 binaries from the
> downloaded .tar.gz file. At the end of the configuration process,
> cmake issues a segmentation fault and no Makefiles are generated.
What project are you configuring?
Can you provide
On 02/03/2016 11:19 AM, Thompson, KT wrote:
> The Windows installation doesn’t appear to provide all the
> required dependencies. ‘cmake-gui’ will not launch and provides
> the error “Qt5Widgets.dll is missing form your computer.”
Ugh, after months of working correctly on the nightly binary
On 02/03/2016 01:03 PM, Adam Rankin wrote:
> Is there documentation on best practices for writing findxyz modules?
There is a section in the cmake-developer manual:
https://cmake.org/cmake/help/v3.5/manual/cmake-developer.7.html#find-modules
> How does a client determine the target names that
Hi Yi-Hong,
Can you try to add the following: -DCMAKE_SYSTEM_VERSION=8.1 to your parameters?
From: Yi-Hong Lyu [mailto:b95705...@ntu.edu.tw]
Sent: Wednesday, February 3, 2016 11:11
To: Gilles Khouzam
Cc: Nicholas Braden ; cmake@cmake.org
35 matches
Mail list logo