• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)


  • Subject: Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)
  • From: Andrew Pontious <email@hidden>
  • Date: Mon, 3 Oct 2005 10:07:19 -0700

On Sep 28, 2005, at 11:09 AM, Mark Alldritt wrote:

I'm trying to get the OMNI Frameworks to build, and I've run into a problem
with the FRAMEWORK_SEARCH_PATHS setting.


I'm trying to configure OmniFoundation and OmniAppKit so that they reference
the other OMNI frameworks. I've been able to configure the projects so that
they build the other frameworks on which they depend, but I cannot get the
#include <OmniBase/OmniBase.h> and #include
<OmniFoundation/OmniFoundation.h> statements to work.

The only way I've ever built the Omni frameworks, for a home project I was working on, is using a common build products location.


This needs to be set for all of Xcode, not just for a particular project or target. Go to the Preferences window -> Build panel.

Hope that helps,

-- Andrew Pontious

I've been trying to use the FRAMEWORK_SEARCH_PATHS setting to make this
work, but it appears to have no effect. I've tried all the different path
combinations I can think of:


$(SRCROOT)/../OmniBase/build/**
$(SRCROOT)/../OmniBase/build/Development

Nothing seems to work.  What am I missing here.  The documentation for
FRAMEWORK_SEARCH_PATHS in the Xcode 2.1 Users Guide states:

Framework Search Paths (FRAMEWORK_SEARCH_PATHS)

This is a list of paths to folders containing frameworks to be searched by the
compiler for both included or imported header files when compiling g C,
Objective-C, C++, or Objective-C++, and by the linker for frameworks used by
the product.

This seems like the thing that I need, but I cannot figure out how to make
it work.


Cheers
-Mark

---------------------------------------------------------------------- --
Mark Alldritt Late Night Software Ltd.
Phone: 250-380-1725 Script Debugger 3.0 - AppleScript IDE
WEB: http://www.latenightsw.com/ FaceSpan 4.2 - AppleScript RAD
Affrus 1.0 - Perl Debugging



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)
      • From: "Timothy J. Wood" <email@hidden>
    • Re: Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)
      • From: Scott Tooker <email@hidden>
  • Prev by Date: Re: GetAliasSize vs. sliasSize
  • Next by Date: Relocation entry errors on 10.3.9
  • Previous by thread: Re: How do I build universal binaries for libraries with endian-specific code
  • Next by thread: Re: Building Omni Frameworks (Was: Xcode 2.1 FRAMEWORK_SEARCH_PATHS?)
  • Index(es):
    • Date
    • Thread