• 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
Re: How do I get dependent unit tests to work for non-framework projects?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do I get dependent unit tests to work for non-framework projects?


  • Subject: Re: How do I get dependent unit tests to work for non-framework projects?
  • From: Mike Laster <email@hidden>
  • Date: Thu, 8 Dec 2005 14:20:33 -0500

It seems the default scripts don't bother to set DYLD_FRAMEWORK_PATH
in the non-framework case, which causes the failure.

I was able to work around this bug by changing the script on the test bundle to:

# Run the unit tests in this test bundle.
DYLD_FRAMEWORK_PATH=${BUILT_PRODUCTS_DIR}
export DYLD_FRAMEWORK_PATH
"${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests"
 _______________________________________________
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

References: 
 >How do I get dependent unit tests to work for non-framework projects? (From: Mike Laster <email@hidden>)

  • Prev by Date: xcodebuild "assertion failed" errors, can't build working project
  • Next by Date: virtual method hidden
  • Previous by thread: How do I get dependent unit tests to work for non-framework projects?
  • Next by thread: xcodebuild "assertion failed" errors, can't build working project
  • Index(es):
    • Date
    • Thread