search

timthedevguy / BGHUDAppKit

* BGHUDAPPKIT is no longer under development by me, I hope that the community will keep it alive and going as I no longer have time to dedicate to the project** The missing HUD controls. Please scroll down to read the readme file for an important notice concerning the future of BGHUDAppKit. Note that there are multiple versions available, 10.5+, 10.6.7, and now 10.7. As soon as I learn how I'll make these all one code base if possible.
http://www.binarymethod.com/
312 stars 57 forks source link

unable to resolve warnings 'directory not found' #43

Closed lulu10 closed 13 years ago

lulu10 commented 13 years ago

i want to clean up these warnings in my project of 'directory not found' on installs of BGHUDAppKit. i'm assuming that somehow a flag for these directories was created when i did have your framework installed.

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-7eabd30 2/build/Debug' following -F not found

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-afad22f/build/Release' following -F not found

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-acafd40/build/Release' following -F not found

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-acafd40/build/Release_10.6_10.5_32_64_GC_embed' following -F not found

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-96612b3/build/Debug' following -F not found

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-96612b3/build/Release' following -F not found

It seems that installing and then removing your framework has left this trail behind.

how can i fix this?

ld: warning: directory '/Volumes/Dev/prep_wc/Prep/../../binarygod-BGHUDAppKit-96612b3/build/Release_10.6_10.5_32_64_GC_embed' following -F not found

maicki commented 13 years ago

Search in the target settings under the "Framework Search Path" for paths that are not existing anymore

timthedevguy commented 13 years ago

Correct, this isn't something BGHUDAppKit did, it's something XCode does automagicly when you add a Framework. It adds the framework path to "Framework Search Path".

As maicki says just remove any mentions of a BGHUDAppKit path from that setting.

Should work after that! ;)

lulu10 commented 13 years ago

thank you both for the info. that worked!