Jeroen Dierckx wrote:
I noticed that libraries are put into the link flags. They don't show up
in the "Linked Libraries" list of the target's info. Could it be that
everything works correctly if we could libraries there? I think XCode
does some extra logic in that case, as opposed to librari
Hi,
On Sun, Nov 8, 2009 at 5:04 AM, Bill Hoffman wrote:
> Daniel Dunbar wrote:
>
>> Hi Bill,
>>
>> Thanks for the reply.
>>
>> The uses I'm seeing aren't on external targets, they are for internal
>> libraries which are built during the build. Is this the same problem?
>>
>> Pretty much the same
Daniel Dunbar wrote:
Hi Bill,
Thanks for the reply.
The uses I'm seeing aren't on external targets, they are for internal
libraries which are built during the build. Is this the same problem?
Pretty much the same problem. A lot of it has to do with static
libraries, if you link a target to a
Hi Bill,
Thanks for the reply.
The uses I'm seeing aren't on external targets, they are for internal
libraries which are built during the build. Is this the same problem?
Also, do you know if anyone has filed a bug with Apple tracking this issue?
- Daniel
On Sat, Nov 7, 2009 at 6:10 PM, Bill
Daniel Dunbar wrote:
Hi,
I've been looking at the CMake generated Xcode project files and I'm
wondering if the dependency hacks (XCODE_DEPEND_HELPER.make) are
absolutely necessary in newer versions of Xcode. That file has some
comment about avoiding a bug in Xcode 1.5 -- is it possible to
genera
Hi,
I've been looking at the CMake generated Xcode project files and I'm
wondering if the dependency hacks (XCODE_DEPEND_HELPER.make) are
absolutely necessary in newer versions of Xcode. That file has some
comment about avoiding a bug in Xcode 1.5 -- is it possible to
generate Xcode 2.0+ specific
