Hello,
Please review the topic GNUInstallDirs_debian-multiarch-fix
GNUInstallDirs: Fix CMAKE_INSTALL_LIBDIR on Debian
When not installing in /usr (i.e. /usr/local) on Debian/Ubuntu, the
multiarch path is not in ldconfig path, and therefore libraries cannot
be found, unless the user manually
Eric Wing wrote:
On 1/10/14, Stephen Kelly
steve...@gmail.com wrote:
Vince Harron wrote:
Android.mk files allow you to target multiple processor
architectures/variants in one make invocation without any reconfiguring
or
multiple build folders. All of those binaries are embedded into one
On 10/01/14 21:19, Alexander Neundorf wrote:
Should the full version 1.2.3 be put into PROJECT_VERSION or
PROJECT_VERSION_STRING ?
Both forms are used in different places in cmake.
I usually consider PROJECT_VERSION = Major.Minor.Patch and
PROJECT_VERSION_STRING as a customizable string that
On 01/13/2014 03:45 AM, Daniele E. Domenichelli wrote:
Please review the topic GNUInstallDirs_debian-multiarch-fix
GNUInstallDirs: Fix CMAKE_INSTALL_LIBDIR on Debian
This looks like a good fix but some details need adjustment.
This hunk:
-if(NOT DEFINED CMAKE_INSTALL_LIBDIR)
removes the
On 13/01/14 15:34, Brad King wrote:
This hunk:
-if(NOT DEFINED CMAKE_INSTALL_LIBDIR)
removes the guard that avoids doing all the default-computing
logic when there is already a value. In this hunk:
+set(CMAKE_INSTALL_LIBDIR ${_LIBDIR_DEFAULT} CACHE PATH object code
libraries
Clinton,
Please take a look at this change:
https://github.com/Kitware/CMake/pull/81
git fetch https://github.com/sryze/CMake var-type-autofill
and integrate it if it makes sense.
Thanks,
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
On 01/13/2014 09:47 AM, Daniele E. Domenichelli wrote:
The problem comes when you change the CMAKE_INSTALL_PREFIX:
When you run cmake (with no -DCMAKE_INSTALL_PREFIX=... argument),
CMAKE_INSTALL_PREFIX is set to /usr/local, and the CMAKE_INSTALL_LIBDIR
is set to lib.
If later you want to
On 13/01/14 15:57, Brad King wrote:
On 01/13/2014 09:47 AM, Daniele E. Domenichelli wrote:
The problem comes when you change the CMAKE_INSTALL_PREFIX:
When you run cmake (with no -DCMAKE_INSTALL_PREFIX=... argument),
CMAKE_INSTALL_PREFIX is set to /usr/local, and the CMAKE_INSTALL_LIBDIR
is
On 01/13/2014 10:23 AM, Daniele E. Domenichelli wrote:
Can I store CMAKE_INSTALL_PREFIX in an internal cached variable, check
if it was changed since last run (i.e. CMAKE_INSTALL_PREFIX_OLD !=
CMAKE_INSTALL_PREFIX), check if the value is the default one, and
eventually force-set it to the new
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14694
==
Reported By:Geoff
Assigned To:
On Friday 10 January 2014, Alexander Neundorf wrote:
On Friday 10 January 2014, Brad King wrote:
On 01/06/2014 04:41 PM, Alexander Neundorf wrote:
I modified write_basic_package_version_file() accordingly, so that you
can now simply do
project(Foo VERSION 1.2.3)
...
work around; use #25; which is the xml code for % to escape it; It
needs to be encoded on the output to the visual studio XML
project/solution
On Mon, Jan 13, 2014 at 8:37 AM, Mantis Bug Tracker
man...@public.kitware.com wrote:
The following issue has been SUBMITTED.
Has anyone else tried running QtCreator (3.0) on windows with cmake master?
I tried and got Qt Creator has no kits that are suitable for CMake
projects. Please configure a kit.
When I checkout and build cmake release this goes away.
I assume QtCreator expects some specific output from cmake
13 matches
Mail list logo