On 09/20/2014 11:53 PM, Nils Gladitz wrote:
On 20.09.2014 23:31, Roland Schulz wrote:
it would be nice if there were a way to emulate rpath under Windows.
As far as I can see there are two possible approaches:
- Generate a shell script which sets PATH
- Generate a manifest for the application
Hi (especially Alex),
I noticed that the automoc target is run each time, even for a trivial
project:
cmake_minimum_required(VERSION 2.8)
project(automoctest)
set(CMAKE_AUTOMOC ON)
find_package(Qt5Widgets REQUIRED)
add_executable(main main.cpp)
target_link_libraries(main Qt5::Widgets)
Hi!
My company is organizing soon a hack week where each employee is able to
work on any project he wants. So, I've decided to work with Cmake and
improve support for iOS to help the product team getting rid of manual
project files, constant merge conflicts and bad project file documentation,
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15170
==
Reported By:stopiccot
Assigned To:
The lowest hanging fruit would be to transition over to setting the
global variable CMAKE_MACOSX_BUNDLE which is used to initialize the
MACOSX_BUNDLE property on all the targets. CMake also supports
CMAKE_XCODE_ATTRIBUTE global variables to allow easy code signing etc.
Lastly have you looked at
What is the problem that this feature is trying to solve?
It seems unnecessary to me as a first-class feature of CMake. I must
be missing something...
But if you do pursue something like this, it seems to me that
install(TARGETS ...) should install all files including the wrapper.
Is this only
On 09/23/2014 03:11 PM, David Cole wrote:
What is the problem that this feature is trying to solve?
Being able to run binaries with DLL dependencies within the build tree.
Basically the same thing that the build time RPATH feature does on e.g.
linux.
If you are e.g. linking to Qt5 (shared)
On 9/23/2014 8:09 AM, Robert Maynard wrote:
The lowest hanging fruit would be to transition over to setting the
global variable CMAKE_MACOSX_BUNDLE which is used to initialize the
MACOSX_BUNDLE property on all the targets. CMake also supports
CMAKE_XCODE_ATTRIBUTE global variables to allow easy
That said it would be really cool to beef up the xcode support enough to
be able to create an actual ios app. I have not dug into that enough.
Should be able to do most of it with CMAKE_XCODE_ATTRIBUTE. I will
look into this try_compile COPY_FILE issue today and get back to the list.
It
On 23 Sep 2014, at 16:56, Bill Hoffman bill.hoff...@kitware.com wrote:
That said it would be really cool to beef up the xcode support enough to
be able to create an actual ios app. I have not dug into that enough.
Should be able to do most of it with CMAKE_XCODE_ATTRIBUTE. I will
look
On 9/23/2014 11:42 AM, Florent Castelli wrote:
I also have a couple of patches for finding the binary during a try_compile
that works with my other change to have an extra variable for the
add_executable and I would need to change it.
It's mostly changing cmCoreTryCompile::FindOutputFile() and
On 23.09.2014 19:12, Roland Schulz wrote:
Have you got a solution to the problem you mentioned in your first email:
I suppose it might be slightly more complex given that the import
library that is being linked to and the DLL that corresponds to the
import library might not be in
On Tuesday, September 23, 2014 09:58:58 Stephen Kelly wrote:
Hi (especially Alex),
I noticed that the automoc target is run each time, even for a trivial
project:
cmake_minimum_required(VERSION 2.8)
project(automoctest)
set(CMAKE_AUTOMOC ON)
find_package(Qt5Widgets REQUIRED)
13 matches
Mail list logo
