On Mar 4, 2012, at 3:29 PM, Stephen Kelly wrote:
Stephen Kelly steveire@... writes:
Brad King wrote:
The implementation is not what I had in mind when I said implies
the platform-specific property. This should be its own property
that one can set/get normally with no special
Brad King wrote:
On 3/4/2012 5:29 PM, Stephen Kelly wrote:
I happened to read a little bit about CPack recently
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overview
The recommendation is to not use MACOSX_BUNDLE when using cpack, so I
thought maybe that makes it different enough
On 3/5/2012 9:42 AM, Stephen Kelly wrote:
Ok. I have pushed win32_executable-and-macosx_bundle-initializers to stage.
Thanks.
Can I go ahead and merge that to next?
Almost. This hunk misses spaces after the period:
- about creation of the Info.plist file for the application
Brad King wrote:
Fix that and then merge.
Done, thanks,
Steve.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Clinton Stimpson wrote:
I happened to read a little bit about CPack recently
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overview
The recommendation is to not use MACOSX_BUNDLE when using cpack,
I don't see that as a general recommendation for GUI applications on Mac
OS X.
2012/3/5 Stephen Kelly steve...@gmail.com:
Clinton Stimpson wrote:
I happened to read a little bit about CPack recently
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overview
The recommendation is to not use MACOSX_BUNDLE when using cpack,
I don't see that as a general
Eric Noulard wrote:
2012/3/5 Stephen Kelly steve...@gmail.com:
Clinton Stimpson wrote:
I happened to read a little bit about CPack recently
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overview
The recommendation is to not use MACOSX_BUNDLE when using cpack,
I don't see that
Stephen Kelly steveire@... writes:
Brad King wrote:
The implementation is not what I had in mind when I said implies
the platform-specific property. This should be its own property
that one can set/get normally with no special C++-implemented
mapping to the other two properties.
On 2/19/2012 4:57 PM, Stephen Kelly wrote:
I've implemented this in my gitorious clone:
https://gitorious.org/~steveire/cmake/steveires-cmake/commits/executable_gui-property
I am not sure whether you want getting the EXECUTABLE_GUI property to work
for the cross-platform abstraction too.
Brad King wrote:
On 2/17/2012 9:27 AM, Stephen Kelly wrote:
Then add SetPropertyDefault in the initialization of EXECUTABLE targets
so that
set(CMAKE_GUI_EXECUTABLE 1)
will change the default for new executable targets in scope of the
variable.
Yes, I had the same idea last night
2012/2/17 Stephen Kelly steve...@gmail.com:
Hi there,
Also in this thread one of the discussion topics was making CMake default to
creating Gui-ready executables. That is, setting the WIN32_EXECUTABLE or
MACOSX_BUNDLE property on the executable target.
Eric Noulard wrote:
2012/2/17 Stephen Kelly
steve...@gmail.com:
Hi there,
Also in this thread one of the discussion topics was making CMake default
to creating Gui-ready executables. That is, setting the WIN32_EXECUTABLE
or MACOSX_BUNDLE property on the executable target.
Brad King wrote:
On 2/17/2012 5:44 AM, Stephen Kelly wrote:
I meant 'default' in the sense of
cmTarget::SetPropertyDefault, in the same way that set(CMAKE_AUTOMOC ON)
sets the AUTOMOC property to true by default for all targets that follow.
[snip]
default value of the property *if*
On 2/17/2012 9:27 AM, Stephen Kelly wrote:
Then add SetPropertyDefault in the initialization of EXECUTABLE targets
so that
set(CMAKE_GUI_EXECUTABLE 1)
will change the default for new executable targets in scope of the
variable.
Yes, I had the same idea last night after emailing.
I can
Hi there,
Also in this thread one of the discussion topics was making CMake default to
creating Gui-ready executables. That is, setting the WIN32_EXECUTABLE or
MACOSX_BUNDLE property on the executable target.
http://thread.gmane.org/gmane.comp.kde.devel.buildsystem/6961/focus=7005
By
15 matches
Mail list logo
