pereraa / iphone-dev

Automatically exported from code.google.com/p/iphone-dev
0 stars 0 forks source link

can't locate framework for: -framework CoreFoundation #140

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

I installed the toolchain on Fedora Core as described on your wiki.
Everything worked fine and I managed to get through all the instructions
without any problems. Then I tried a little sample application I pulled
from somewhere. Compiling the application worked, but linking yielded in
the error message noted in the subject line of this issue.

What is the expected output? What do you see instead?

A compiled and linked application.

What version of the product are you using? On what operating system?

I'm devloping on a vanilla Fedora Core 6.

Please provide any additional information below.

here is the output of my Makefile:

/usr/local/bin/arm-apple-darwin-gcc -lobjc -ObjC -framework CoreFoundation
-framework Foundation -framework CoreGraphics -framework GraphicsServices
-framework UIKit -framework LayerKit -o build/Motion.app/Motion tmp/main.o
tmp/MotionApp.o
/usr/local/bin/arm-apple-darwin-ld: can't locate framework for: -framework
CoreFoundation
collect2: ld returned 1 exit status

Original issue reported on code.google.com by puder1...@gmail.com on 27 May 2008 at 5:03

GoogleCodeExporter commented 8 years ago
I have the same issue, too.
Who knows how to solve it?

Original comment by qwjc...@gmail.com on 29 Dec 2008 at 7:29

GoogleCodeExporter commented 8 years ago
Just look at the manpage of gcc :

-Fdir
           Add the framework directory dir to the head of the list of directories to be searched for header files.  
These directories are interleaved with those
           specified by -I options and are scanned in a left-to-right order.

           A framework directory is a directory with frameworks in it.  A framework is a directory with a "Headers" 
and/or "PrivateHeaders" directory contained
           directly in it that ends in ".framework".  The name of a framework is the name of this directory 
excluding the ".framework".  Headers associated with
           the framework are found in one of those two directories, with "Headers" being searched first.  A 
subframework is a framework directory that is in a
           framework's "Frameworks" directory.  Includes of subframework headers can only appear in a header of 
a framework that contains the subframework, or in
           a sibling subframework header.  Two subframeworks are siblings if they occur in the same framework.  
A subframework should not have the same name as a
           framework, a warning will be issued if this is violated.  Currently a subframework cannot have 
subframeworks, in the future, the mechanism may be
           extended to support this.  The standard frameworks can be found in "/System/Library/Frameworks" and 
"/Library/Frameworks".  An example include looks
           like "#include <Framework/header.h>", where Framework denotes the name of the framework and 
header.h is found in the "PrivateHeaders" or "Headers"
           directory.

Original comment by richard....@gmail.com on 28 Jan 2010 at 9:47