-- Forwarded message --
From: Wen Shi ws...@sfu.ca
Date: Sat, Nov 7, 2009 at 2:19 AM
Subject: Re: [Insight-users] Problem with CMakelist
To: John Drescher dresche...@gmail.com
Hi john,
Thank you for your reply.
But actually I first used INCLUDE(${VXL_USE_FILE})
But when I use
John Drescher wrote:
-- Forwarded message --
From: Wen Shi ws...@sfu.ca
Date: Sat, Nov 7, 2009 at 2:19 AM
Subject: Re: [Insight-users] Problem with CMakelist
To: John Drescher dresche...@gmail.com
Hi john,
Thank you for your reply.
But actually I first used
I have been using
export_library_dependencies()
to incorporate library dependencies when generating configuration
files for use with find_package()
However, I just discovered that this is a deprecated feature, and that
install(EXPORT...)
should be used instead.
However, it is
On Nov 7, 2009, at 11:59 AM, James C. Sutherland wrote:
I have been using
export_library_dependencies()
to incorporate library dependencies when generating configuration
files for use with find_package()
However, I just discovered that this is a deprecated feature, and that
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
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
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 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