Re: [cmake-developers] remove obsolete link directories from SunOS.cmake
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 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 install any content to these directories by > > default > > when you install the Studio package. > > The C++ compiler should automatically do the right thing with regards > > to linking. > > > > The changes were created by Shawn Walker-Salas at Oracle. > > > > Thanks, > > April Chin > > > > -- > > > > 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. For more > > information on each offering, please visit: > > > > CMake Support: http://cmake.org/cmake/help/support.html > > CMake Consulting: http://cmake.org/cmake/help/consulting.html > > CMake Training Courses: http://cmake.org/cmake/help/training.html > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/cmake-developers > -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Add command line options for deprecation message control
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: Michael Scott
Date: Sun, 1 Nov 2015 16:05:15 +
Subject: [PATCH 1/7] Tests: Revise message in RunCMake.CommandLine -Wdev case
Use more prose-like capitalization.
---
Tests/RunCMake/CommandLine/Wdev-stderr.txt | 2 +-
Tests/RunCMake/CommandLine/Wdev.cmake | 2 +-
Tests/RunCMake/CommandLine/Wno-dev.cmake | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Tests/RunCMake/CommandLine/Wdev-stderr.txt
b/Tests/RunCMake/CommandLine/Wdev-stderr.txt
index 92c1d23..88cfb3a 100644
--- a/Tests/RunCMake/CommandLine/Wdev-stderr.txt
+++ b/Tests/RunCMake/CommandLine/Wdev-stderr.txt
@@ -1,5 +1,5 @@
^CMake Warning \(dev\) at Wdev.cmake:1 \(message\):
- Some Author Warning
+ Some author warning
Call Stack \(most recent call first\):
CMakeLists.txt:3 \(include\)
This warning is for project developers. Use -Wno-dev to suppress it.
diff --git a/Tests/RunCMake/CommandLine/Wdev.cmake
b/Tests/RunCMake/CommandLine/Wdev.cmake
index e5026ef..756f31e 100644
--- a/Tests/RunCMake/CommandLine/Wdev.cmake
+++ b/Tests/RunCMake/CommandLine/Wdev.cmake
@@ -1,4 +1,4 @@
-message(AUTHOR_WARNING "Some Author Warning")
+message(AUTHOR_WARNING "Some author warning")
# with -Wdev this will also cause an AUTHOR_WARNING message, checks that
# messages issued outside of the message command, by other CMake commands, also
diff --git a/Tests/RunCMake/CommandLine/Wno-dev.cmake
b/Tests/RunCMake/CommandLine/Wno-dev.cmake
index d81b858..802b435 100644
--- a/Tests/RunCMake/CommandLine/Wno-dev.cmake
+++ b/Tests/RunCMake/CommandLine/Wno-dev.cmake
@@ -1,4 +1,4 @@
-message(AUTHOR_WARNING "Some Author Warning")
+message(AUTHOR_WARNING "Some author warning")
# without -Wno-dev this will also cause an AUTHOR_WARNING message, checks that
# messages issued outside of the message command, by other CMake commands, also
--
2.1.4
From e60002e10f2ea10cadac74bd8c3a2d23cb35be4a Mon Sep 17 00:00:00 2001
From: Michael Scott
Date: Sun, 8 Nov 2015 12:20:47 +
Subject: [PATCH 2/7] Make message suppression more consistent.
Make the message suppression more consistent, by adding a check
for the message related CMake variables in cmake::IssueMessage,
which allows callers of IssueMessage other than the message
command to behave as expected. Also added a check for
CMAKE_SUPPRESS_DEVELOPER_WARNINGS in the message command to
mirror the deprecated message type behaviour.
Added a 'force' flag to the cmake::IssueMessage method, to
make the message suppression consistent, when setting the
message related CMake variables directly in a CMake file.
Expand message command tests to cover the AUTHOR_WARNING message
type as well.
---
Source/cmMakefile.cxx | 8 +--
Source/cmMakefile.h | 3 +-
Source/cmMessageCommand.cxx | 12 -
Source/cmake.cxx | 70 ++-
Source/cmake.h| 12 -
Tests/RunCMake/message/nomessage.cmake| 5 ++
Tests/RunCMake/message/warnmessage-stderr.txt | 11 -
Tests/RunCMake/message/warnmessage.cmake | 6 ++-
8 files changed, 103 insertions(+), 24 deletions(-)
diff --git a/Source/cmMakefile.cxx b/Source/cmMakefile.cxx
index a1f143a..fd93a41 100644
--- a/Source/cmMakefile.cxx
+++ b/Source/cmMakefile.cxx
@@ -130,7 +130,8 @@ cmMakefile::~cmMakefile()
//
void cmMakefile::IssueMessage(cmake::MessageType t,
- std::string const& text) const
+ std::string const& text,
+ bool force) const
{
// Collect context information.
if(!this->ExecutionStatusStack.empty())
@@ -139,7 +140,8 @@ void cmMakefile::IssueMessage(cmake::MessageType t,
{
this->ExecutionStatusStack.back()->SetNestedError(true);
}
-this->GetCMakeInstance()->IssueMessage(t, text, this->GetBacktrace());
+this->GetCMakeInstance()->IssueMessage(t, text, this->GetBacktrace(),
+ force);
}
else
{
@@ -154,7 +156,7 @@ void cmMakefile::IssueMessage(cmake::MessageType t,
lfc.FilePath = converter.Convert(lfc.FilePath, cmOutputConverter::HOME);
}
lfc.Line = 0;
-this->GetCMakeInstance()->IssueMessage(t, text, lfc);
+this->GetCMakeInstance()->IssueMessage(t, text, lfc, force);
}
}
diff --git a/Source/cmMakefile.h b/Source/cmMakefile.h
index 4215b72..e89f772 100644
--- a/Source/cmMakefile.h
+++ b/Source/cmMakefile.h
@@ -719,7 +719,8 @@ public:
};
void IssueMessage(cmake::MessageType t,
-std::string const& t
Re: [cmake-developers] remove obsolete link directories from SunOS.cmake
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. I'm not objecting to your patch - I'm trying to provide more feedback and maybe someone can chime in why it was this way before. In ccs I'm only seeing libcurses.so libform.so libgen.so libl.so libmalloc.so libmenu.so libpanel.solibtermcap.so libtermlib.so liby.so From that list curses symlink ends up pointing back to /lib/libcurses.so.1 anyway. And if we really want to get sticky - those dir/ are 32bit only. So if you were building a 64bit application/lib it wouldn't have been useful at all. On Sat, Nov 14, 2015 at 2: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 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 install any content to these directories by >> default >> when you install the Studio package. >> The C++ compiler should automatically do the right thing with regards >> to linking. >> >> The changes were created by Shawn Walker-Salas at Oracle. >> >> Thanks, >> April Chin >> >> -- >> >> 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. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/cmake-developers -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] remove obsolete link directories from SunOS.cmake
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 install any content to these directories by > default > when you install the Studio package. > The C++ compiler should automatically do the right thing with regards > to linking. > > The changes were created by Shawn Walker-Salas at Oracle. > > Thanks, > April Chin > > -- > > 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. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake-developers -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] remove obsolete link directories from SunOS.cmake
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 right thing with regards
to linking.
The changes were created by Shawn Walker-Salas at Oracle.
Thanks,
April Chin
From 94fc4f94337be059e9e99bf5ae5ad377370ca0e2 Mon Sep 17 00:00:00 2001
From: April Chin
Date: Fri, 13 Nov 2015 11:35:58 -0800
Subject: [PATCH] Remove obsolete Studio compiler library directories
---
Modules/Platform/SunOS.cmake | 6 --
1 file changed, 6 deletions(-)
diff --git a/Modules/Platform/SunOS.cmake b/Modules/Platform/SunOS.cmake
index 77946f2..58398c0 100644
--- a/Modules/Platform/SunOS.cmake
+++ b/Modules/Platform/SunOS.cmake
@@ -9,12 +9,6 @@ endif()
include(Platform/UnixPaths)
-# Add the compiler's implicit link directories.
-if("${CMAKE_C_COMPILER_ID} ${CMAKE_CXX_COMPILER_ID}" MATCHES SunPro)
- list(APPEND CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES
-/opt/SUNWspro/lib /opt/SUNWspro/prod/lib /usr/ccs/lib)
-endif()
-
# The Sun linker needs to find transitive shared library dependencies
# in the -L path.
set(CMAKE_LINK_DEPENDENT_LIBRARY_DIRS 1)
--
2.6.1
--
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. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] MSVC dll define global variables as well as functions?
On 11/13/2015 2:14 PM, Richard Thiebaud via cmake-developers wrote: When building a DLL with MSVC, CMAKE 3.4 can now auto-create a .def file for all functions in the DLL, but global variables or static class variables are not included in the .def file. Could the .def file be created with def's for the variables as well as the functions? See my blog on the topic: http://www.kitware.com/blog/home/post/939 Short answer is no, it is not possible. The def file has all of that stuff. The problem is the calling code needs to know. That is stuff linking to the dll needs to know at compile time if the global variable is in a dll or not. -Bill -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] MSVC dll define global variables as well as functions?
When building a DLL with MSVC, CMAKE 3.4 can now auto-create a .def file for all functions in the DLL, but global variables or static class variables are not included in the .def file. Could the .def file be created with def's for the variables as well as the functions? -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] C++11 support?
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 actually build with flags for C++11 on several compilers and use C++11 conditionally in a few places for optimizations, but there is always a C++98 fallback. -Brad -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] C++11 support?
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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Visual Studio 2013 with CMake GUI on Windows
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" : > 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 containing CMAKE_PREFIX_PATH to the path to > msvc2013_64_opengl and it should be found automatically. > Ensure Qt5Widgets_DIR points to > > msvc2013_64_opengl/lib/cmake/Qt5Widgets > > -Brad -- Regards, Konstantin Podsvirov -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Visual Studio 2013 with CMake GUI on Windows
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? > > CMake already supports being built with Qt5 on Windows. > > Configure with CMAKE_PREFIX_PATH containing to the path to > msvc2013_64_opengl and it should be found automatically. > Ensure Qt5Widgets_DIR points to > > msvc2013_64_opengl/lib/cmake/Qt5Widgets Thank you Brad, I wasn't setting CMAKE_PREFIX_PATH because it didn't show up by default in the list of cache variables after generating. I added it manually and it just worked. At first all I was doing was enabling QT dialog in config, regenerating, and then changed the path that it wanted for qtmake.exe. When I pointed it at qtmake for Qt5, it complained about requiring Qt4. -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Visual Studio 2013 with CMake GUI on Windows
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 CMAKE_PREFIX_PATH containing to the path to msvc2013_64_opengl and it should be found automatically. Ensure Qt5Widgets_DIR points to msvc2013_64_opengl/lib/cmake/Qt5Widgets -Brad -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Visual Studio 2013 with CMake GUI on Windows
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 not have VS 2008 or 2010 available, unfortunately. I also do not have a linux or mac platform to build on. -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] XCode Unit Test Bundle targets support
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] XCode Unit Test Bundle targets support 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 those myself but we do have these since 3.3: https://cmake.org/cmake/help/v3.4/module/FindXCTest.html https://cmake.org/cmake/help/v3.4/prop_tgt/XCTEST.html -Brad -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] XCode Unit Test Bundle targets support
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 those myself but we do have these since 3.3: https://cmake.org/cmake/help/v3.4/module/FindXCTest.html https://cmake.org/cmake/help/v3.4/prop_tgt/XCTEST.html -Brad -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] iOS Framework Bundle support
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 (for our project). Do you know what caused performance improve in Cmake 3.2 ? We are using Makefile builds for automatic tests on farm of devices/simulators. We strongly believe that Xcode generation should only be used for IDE context and not for Continuous Integration/cmd usage. In cmd/CI case you want to use generators like make, ninja, fastbuild, etc. What is your opinion about that? Best Regards Bartosz -Original Message- From: Gregor Jasny [mailto:gja...@gmail.com] Sent: Friday, November 13, 2015 2:09 PM To: Bartosz Kosiorek; cmake-developers@cmake.org Subject: Re: [cmake-developers] [PATCH] iOS Framework Bundle support 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. Download and install CMake 3.4.0 > 2. Unpack and unpack cmake_shared_ios_framework.zip 3. cd > cmake_shared_ios_framework 4. mkdir build 5. cd build 6. > ../../../cmake-3.4.0-rc3-Darwin-x86_64/CMake.app/Contents/bin/cmake .. > 7. make I wonder why anyone wants to build for iOS without the Xcode generator? -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] iOS Framework Bundle support
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. Download and install CMake 3.4.0 > 2. Unpack and unpack cmake_shared_ios_framework.zip > 3. cd cmake_shared_ios_framework > 4. mkdir build > 5. cd build > 6. ../../../cmake-3.4.0-rc3-Darwin-x86_64/CMake.app/Contents/bin/cmake .. > 7. make I wonder why anyone wants to build for iOS without the Xcode generator? -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] iOS Framework Bundle support
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 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015846]: External make file usage
The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15846 == Reported By:Valerii Kanunik Assigned To: == Project:CMake Issue ID: 15846 Category: CMake Reproducibility:have not tried Severity: feature Priority: normal Status: new == Date Submitted: 2015-11-13 07:49 EST Last Modified: 2015-11-13 07:49 EST == Summary:External make file usage Description: Is it possible add for instance 'include_external_gnumake' command for adding exciting or previously created Makefile? As a result it should add target name that can be used in the add_dependencies command. And all make commands like 'make all' or 'make clean' and others just should be forced to added directory similar to make -C . == Issue History Date ModifiedUsername FieldChange == 2015-11-13 07:49 Valerii KanunikNew Issue == -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released
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 packaging. Does this mean that the ubuntu package manager will stop complaining of CPack DEBs ? As the author of those patches announced the packages can even be built for Launchpad: https://www.mail-archive.com/cmake-developers%40cmake.org/msg14723.html The packages can be created to pass lint tests but there are no convenience functions that would create a license file and such so only setting package components in install commands, adding deb package generator and create package won't produce a package that would pass lintian tests. So yes it can be done but for now it's not as straight forward as it could be. Indeed, but please note that for being able to support multipackaging (ie. creating multiple valid components on eg. Launchpad), the patch with the Source field is still needed (which was included post 3.4 freeze). At least, this is enough for having your packages built on your own ppa on Launchpad (3.4.1 should include the Source field as well). Note: the new version of cmake should also be referenced by your PPA. Raffi -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released
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 ubuntu package manager will stop complaining of > CPack DEBs ? As the author of those patches announced the packages can even be built for Launchpad: https://www.mail-archive.com/cmake-developers%40cmake.org/msg14723.html The packages can be created to pass lint tests but there are no convenience functions that would create a license file and such so only setting package components in install commands, adding deb package generator and create package won't produce a package that would pass lintian tests. So yes it can be done but for now it's not as straight forward as it could be. Regards, Domen -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
