Re: Cocoa Newbie Question.

On Wed, 11 Jun 2008 23:14:31 +0200, Reinder Verlinde wrote:
> In article 
><fe79dd66-0263-429a-b443-a7a28ef083eb@[EMAIL PROTECTED]
>,
>  piscesboy <oraclmaster@[EMAIL PROTECTED]
> wrote:

>> > gcc -Wno-im****t -ansi -pedantic -Wall -O2 -c treenode.c
>> > gcc -Wno-im****t -ansi -pedantic -Wall -O2 -c main.m

> This is not the cause of your error, but -Wno-im****t very, very likely 
> is not something that you will want to compile .m files with. At the 
> least, that would get rid of the warning

>> > main.m:1:2: warning: #im****t is a GCC extension

> I also guess that you are not using Xcode. Reason is that, on my system 
> (10.5.3), Xcode compiles a simple main.m as

> CompileC /[...]/main.o /[...]/main.m normal ppc objective-c 
> com.apple.compilers.gcc.4_0

> which eventually calls gcc passing a few zillion flags, including

>     -fpascal-strings
>     -x objective-c
>     -arch i386

> If you are not using Xcode, start doing that, if only to check what 
> command lines it produces.

For what it's worth, I have been able to compile some tiny Cocoa apps
using commands such as

	cc -Wall -c -o MyClass.o MyClass.m
	cc -Wall -c -o main.o main.m
	cc -Wall MyClass.o main.o -framework Cocoa -o MyApp

where the files all contain

	#im****t <Cocoa/Cocoa.h>

and the resulting MyApp is just a simple executable file that puts up a
window, but it doesn't contain any resources such as a true Cocoa app
would have.


> If this does not help, start compiling a main.m that only contains 
> "im****t <Cocoa/Cocoa.h>". If that succeeds, the problem likely is with 
> some of your own files or with the commands you issue to compile your 
> code.

> Reinder


-- 
Dave Seaman
Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
<http://www.indybay.org/newsitems/2008/03/29/18489281.php>