Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I think the title is pretty clear. I have ran into this twice now.
The first time it indicated a problem, and my project wouldn’t compile.
The second time everything still worked.
Is it just a fluke if my code still builds when this turns red?
Anything in the files and groups list that turns red indicates a missing file or directory. This is not necessarily cause for concern, because in many instances the file is expected to be built as part of your build process.
In the case of your linked static library, you are probably depending on a second target or project to build the static library. When you changed build configurations, Xcode noticed that it had not yet been built, so it shows it as red. When you built the project and the dependent library was itself built, it turned black again.