Le 13/11/15 09:30, Domen Vrankar a écrit :
2015-11-12 22:52 GMT+01:00 Jean-Michaël Celerier
:
* The "CPackDeb" module now correctly excludes symlinks during
package checksum calculation.
* The "CPackDeb" no longer uses fakeroot and system tar program for
2015-11-12 22:52 GMT+01:00 Jean-Michaël Celerier
:
>> * The "CPackDeb" module now correctly excludes symlinks during
> package checksum calculation.
>
>> * The "CPackDeb" no longer uses fakeroot and system tar program for
> packaging.
>
> Does this mean that the
CMake requires Qt4, which is incompatible with VS 2013 officially. I
do not want to apply patches to get it working.
Is it possible to get CMake to use Qt5? I know this already supports
VS 2013. Is Qt5 backward compatible with Qt4 with regards to the
feature sets being utilized by CMake?
I do
On 11/13/2015 11:42 AM, Robert Dailey wrote:
> CMake requires Qt4, which is incompatible with VS 2013 officially. I
> do not want to apply patches to get it working.
>
> Is it possible to get CMake to use Qt5?
CMake already supports being built with Qt5 on Windows.
Configure with
Ok thanks, we'll check it out!
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Friday, November 13, 2015 9:14 AM
To: Robert Goulet
Cc: cmake-developers@cmake.org; Gregor Jasny
Subject: Re: [cmake-developers]
Hello,
The following patch has been tested with cmake 3.3.2 built on Solaris.
It removes obsolete link directories from SunOS.cmake.
Studio compilers no longer install any content to these directories by
default
when you install the Studio package.
The C++ compiler should automatically do the
On Fri, Nov 13, 2015 at 10:53 AM, Brad King wrote:
> On 11/13/2015 11:42 AM, Robert Dailey wrote:
>> CMake requires Qt4, which is incompatible with VS 2013 officially. I
>> do not want to apply patches to get it working.
>>
>> Is it possible to get CMake to use Qt5?
>
>
On 11/13/2015 01:08 PM, Robert Dailey wrote:
> Just to be clear, does CMake code base allow for C++11 or higher?
> or are you guys locked down to C++03?
The latter. We don't allow C++11 in our main source code yet.
We still support hosting builds on compilers that do not support it.
We do
What exact version of Solaris and SS did you test?
On Sat, Nov 14, 2015 at 2:52 AM, A Chin wrote:
> Hello,
>
> The following patch has been tested with cmake 3.3.2 built on Solaris.
>
> It removes obsolete link directories from SunOS.cmake.
> Studio compilers no longer
Just to be clear, does CMake code base allow for C++11 or higher? or
are you guys locked down to C++03?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community.
What's the noise?..
QtDialog (cmake-gui) has long been going with Qt5 and the deployment in Windows
was solved also.
Here is the latest announce CMake 3.4.0 (MSVC2013 and Qt 5.5.1):
http://public.kitware.com/pipermail/cmake-developers/2015-November/026931.html
13.11.2015, 19:53, "Brad King"
I tested using Solaris Studio 12.4 on our latest Solaris development
release,
post Solaris 11 Update 3.
On Fri, Nov 13, 2015 at 11:56 AM, C Bergström
wrote:
> What exact version of Solaris and SS did you test?
>
> On Sat, Nov 14, 2015 at 2:52 AM, A Chin
Hi Brad,
Here's the original patch split up into smaller more specific patches.
Let me know if there's any issues or if everything's okay, so I can
continue with the rest of the intended changes.
Cheers,
Michael
From 48d8c38c7b5724e4b6b53fa8647046c96cec603b Mon Sep 17 00:00:00 2001
From:
At a glance - I'd 1/2 agree with you on what SS will do.
/opt/SUNWspro/lib /opt/SUNWspro/prod/lib - These or corresponding dir/
should be added automatically
/usr/ccs/lib - I don't know if this will be added by default. crle
isn't showing it on a default system. I didn't check the SS link line.
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15846
==
Reported By:Valerii Kanunik
Assigned To:
Hello.
Main reason for using Makefile instead of Xcode is performance reason. Xcode
generator is much slower that Makefile in our project.
The performance was improved in Cmake 3.2 but still it is much slower on Xcode.
Similar slowness could be observed on Windows with Visual Studio generator
On 11/12/2015 12:47 PM, Robert Goulet wrote:
> In XCode we can add a target of type “Test”, specifically for us is
> the “iOS Unit Test Bundle” that is interesting, because with it we
> can write iOS test cases that will install, launch and close the app
> on the iOS device.
I'm not familiar with
On 12/11/15 09:25, Bartosz Kosiorek wrote:
> With this tiny little patch, the correct directory structure for iOS
> Frameworks is created.
I made the patch even smaller and pushed it into the
non-xcode-framework-layout topic branch. There I also added a test.
Thanks,
Gregor
--
Powered by
On 11/11/15 02:19, Bartosz Kosiorek wrote:
> Hi
>
> Generally I created this cmake scripts to to able to test creating iOS/OSX
> Application Bundle and iOS/OSX Dynamic Framework Bundle.
> By default it produces iOS application Bundle and iOS Framework Bundle.
>
> Steps to reproduce:
> 1.
19 matches
Mail list logo