Nick,
We are using a modification on your patch internally.
Few things
1) It breaks projects that have resources. Fix is to attach the Executable
to only the 'copy to cmake build dir' phase. Even after the mailinglist
discussion I'm unsure of the need for this?
XCode basically claims it is a
and wow, the patch I just sent is broken because cmXCodeObject-Print() has
sideffects! :(
Will send a patch that fixes -Print() when I have some extra time.
/Johan
On Mon, Mar 7, 2011 at 1:33 PM, Johan Björk p...@spotify.com wrote:
Nick,
We are using a modification on your patch internally.
Hi Nick,
Any updates on this patch?
Cheers
/Johan
On Thu, Jan 20, 2011 at 2:08 AM, Nick Kledzik kled...@apple.com wrote:
BTW, it might make more sense to move this to the cmake-developers
mailing list.
I've transfered this thread to the developer list. See below for
continuation..
BTW, it might make more sense to move this to the cmake-developers mailing
list.
I've transfered this thread to the developer list. See below for continuation..
On Jan 18, 2011, at 12:42 PM, Bill Hoffman wrote:
On 1/18/2011 2:40 PM, Brad King wrote:
On 1/18/2011 2:12 PM, Nick Kledzik
On Wed, Jan 19, 2011 at 8:08 PM, Nick Kledzik kled...@apple.com wrote:
BTW, it might make more sense to move this to the cmake-developers mailing
list.
I've transfered this thread to the developer list. See below for
continuation..
On Jan 18, 2011, at 12:42 PM, Bill Hoffman wrote:
On
On Mon, Jan 17, 2011 at 9:02 PM, Nick Kledzik kled...@apple.com wrote:
On Jan 13, 2011, at 1:57 PM, Bill Hoffman wrote:
On 1/13/2011 4:49 PM, Nick Kledzik wrote:
On Jan 13, 2011, at 12:41 PM, Bill Hoffman wrote:
This is because Xcode provides no way to order static libraries as
far as I
I have changes that cause cmake to produce an Xcode project in which the
targets do not have the extra phases, and the dependencies are set up such
that incremental builds work efficiently!
But I'm having some impedance mismatches between where Xcode want the
build results to be and where
Clarification: I was referring to intermediate build product files, not
final libraries and executables. For the most part, nobody should care where
their intermediate files are as long as everything works.
Sorry for the mis-communication.
On Tue, Jan 18, 2011 at 8:30 AM, Bill Hoffman
On Jan 18, 2011, at 5:30 AM, Bill Hoffman wrote:
I have changes that cause cmake to produce an Xcode project in which the
targets do not have the extra phases, and the dependencies are set up such
that incremental builds work efficiently!
But I'm having some impedance mismatches between
On Tue, Jan 18, 2011 at 2:12 PM, Nick Kledzik kled...@apple.com wrote:
On Jan 18, 2011, at 5:30 AM, Bill Hoffman wrote:
I have changes that cause cmake to produce an Xcode project in which
the
targets do not have the extra phases, and the dependencies are set up
such
that incremental
On Jan 18, 2011, at 11:23 AM, David Cole wrote:
That is not entirely true
Things like EXECUTABLE_OUTPUT_PATH and target location properties have
to work without an extra install step. What do you mean CMake expects
to find things in install locations? CMake does need to be able
On Tue, Jan 18, 2011 at 2:30 PM, Nick Kledzik kled...@apple.com wrote:
On Jan 18, 2011, at 11:23 AM, David Cole wrote:
That is not entirely true
Things like EXECUTABLE_OUTPUT_PATH and target location properties have
to work without an extra install step. What do you mean CMake
On 1/18/2011 2:12 PM, Nick Kledzik wrote:
When I use cmake to create a Makefile, the resulting main executable
is placed in the build directory tree next to the Makefile.
This is where CMake puts files in single-configuration generators.
When I use cmake to create a xcode project, the
On 1/18/2011 2:40 PM, Brad King wrote:
On 1/18/2011 2:12 PM, Nick Kledzik wrote:
When I use cmake to create a Makefile, the resulting main executable
is placed in the build directory tree next to the Makefile.
This is where CMake puts files in single-configuration generators.
When I use
On Jan 13, 2011, at 1:57 PM, Bill Hoffman wrote:
On 1/13/2011 4:49 PM, Nick Kledzik wrote:
On Jan 13, 2011, at 12:41 PM, Bill Hoffman wrote:
This is because Xcode provides no way to order static libraries as
far as I can tell, or to repeat them. Also, no way to depend on a
static library or
I'm a long time Xcode user and recently used cmake to create an Xcode project
for LLVM. I really like the idea the CMake can produce native projects for
different platforms, but in my case, the resulting xcode project was very slow
to use.
To investigate, I created a small cmake example
On 1/13/2011 3:16 PM, Nick Kledzik wrote:
I'm a long time Xcode user and recently used cmake to create an Xcode
project for LLVM. I really like the idea the CMake can produce native
projects for different platforms, but in my case, the resulting xcode
project was very slow to use.
To
On 1/13/2011 4:49 PM, Nick Kledzik wrote:
On Jan 13, 2011, at 12:41 PM, Bill Hoffman wrote:
This is because Xcode provides no way to order static libraries as
far as I can tell, or to repeat them. Also, no way to depend on a
static library or a file directly, forcing the makefile usage.
This
18 matches
Mail list logo
