I'm getting the following warning when I try to build my project:
Directory '(directory name)' following -L not found
The directory name refers to an SDK that I had added to my Resources folder, but have since removed. The problem is that I have no idea how to remove the reference to the directory that is causing the warning. I can't find any reference to it anywhere in my build settings.
Can anyone help me? I am using Xcode 3.2.5.
Thank you.
Related
I am new to Xcode so I am probably doing something wrong (or missing something in this case). I would appreciate any help.
I've just created a new project on Xcode. New Project -> macOS -> Command Prompt. I've saved it somewhere and as soon as Xcode returns with its main screen on my project's properties, I've closed it. Then cd'd to the folder where my .xcodeproject was (on terminal) and ran xcodebuild install and it returns me that message. Additionally, I tried editing my project Schema from debug to release and closed Xcode again (to make sure everything was saved), same error.
If I build the project from Xcode's UI it works, obviously, it will print Hello World, but I can't run the builder from command line. Does anyone have any tips? Thank you!
This is on Xcode 8.3.3.
I ran into this issue and my fix was due to an overlooked flag in my .gitlab-ci.yml file.
Pretty easy fix :)
So the error says:
xcodebuild: error: '<some file>' is not a project file.
The reason for that was because in my .gitlab-ci.yml file it said -project instead of -workspace
Super easy to overlook. So if you have the: is not a project file error, make sure your flag says -workspace and not -project.
Alternatively if you have the opposite error xcodebuild: error: '<some file>' is not a workspace file then you'll want to change your -workspace flag to -project
My bad... the xcodebuild install command works from one directory up, outside the .xcodeproj folder.
I am using GMDCircleLoader in my project. I imported(Dragged GMDCircleLoader folder AND clicked on copy and also checked targets) the required folder to my project. I can import the header file and coded what was required.
But when I try to compile, I get the following error in Xcode 7.2 attached as above. The DashboardViewController.m file is already added in the Build Phases/Compile Sources so .m file not compiling is not an issue.
I looked on the net and also learned that this error comes when the related framework is not imported. I have imported frameworks such as QuartzCore, CoreGraphics.
Tried looking for all possible solutions but no luck yet.
Can anyone please help me out.
Thanks in advance.
I'm having the following problem when installing IntelliJ and trying to import a project.
I already installed JDK 7 and JDK 8 and set the JAVA_HOME to point at the right folder:
Monkis-MacBook-Pro-2:Home dalvik$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home
Any help would be much appreceiated
It looks like somewhere in Idea or in your system there is settings which points Java path to your user's home directory - /Users/nativ/bin/java
Which I believe is not the right one and missing.
Check your .bash_profile or any sbt related settings.
Check also jenv project, might be helpful for you.
https://github.com/gcuisinier/jenv
I'm trying to use UIImagePickerController, but I need to include the MobileCoreServices framework in order to do so.
I've placed the import statement in my ViewController.h file:
#import <MobileCoreServices/MobileCoreServices.h>
But I get an error:
"Could not build module MobileCoreServices.h".
I've also already linked the MobileCoreServices framework in the project build phrases, and I see it there on the sidebar in the frameworks folder, but it's still giving me an error.
Does anyone know a solution this?
Nevermind everyone!
This problem was solved by another SO user on another thread:
Could not build module 'UIKit" in cocoapods since Xcode 5.1
Go to your DerivedData directory and remove ModuleCache directory.
In terminal:
cd ~/Library/Developer/Xcode/DerivedData
rm -rf ModuleCache/
Keeping this thread alive in case anyone else runs into this problem in the future.
Thanks!
I just addred Growl integration to an Xcode application. The source compiles and runs correctly under the Debug target while testing.
When I try to build the Release target however, I get the following error and I'm not sure why, or whoe to resolve it.
Building target “EchowavesNotifier” of project “EchowavesNotifier” with configuration “Release” — (1 error)
cd /src/echowaves-notifier-osx
/Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -strip-debug-symbols -resolve-src-symlinks /src/echowaves-notifier-osx/Growl.framework /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks
strip: for architecture x86_64 object: /src/echowaves-notifier-osx/Growl.framework/Versions/A/Growl malformed object (unknown load command 5)
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
Build failed (1 error)
Is it some kind of 64-bit (x86_64) related issue?
I ran into this recently when upgrading Growl, and several other groups have noted it (I found some traffic on the Unison.app list). What seems to be happening is some kind of mismatch at the link step, though I haven't been able to isolate it.
The solution I've found so far is to delete the entire build/ directory and rebuild (which is much more than just doing a "clean" in xcode). So far I have not seen the problem recur for any developer after performing that. Please let me know if this does or doesn't fix your problem, since I want to know whether I need to continue hunting solutions for this problem should it come back.