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 t
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 mismatche
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.
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 may have changed, so, if
> you can s
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 proj
