Re: Xcode claims it can't find source files which exist
Re: Xcode claims it can't find source files which exist
- Subject: Re: Xcode claims it can't find source files which exist
- From: Nicholas Rinard <email@hidden>
- Date: Sat, 12 Nov 2005 17:38:08 -0500
i hope you're not suggesting that i haven't tried building the app a
second time? that's what your comment sounds like to me. obviously i
have tried building over a hundred times with a hundred different
configurations and tweaks.
i updated xcode to v2.2 and am having the same issue with it.
xcode simply absolutely will not deal with more than 136 source files
+ library files. i tried changing the paths to the files and really
long paths seem to decrease this number, meaning that if i put the
source halfway across my hard drive, xcode will only deal with ~75
files. but moving them closer to xcode, like only one directory away,
doesn't seem to increase it.
this is a retarded question, but can anyone verify building a Java
Swing app with Xcode having more than, say, 150 source files?
(am i really the only person ever to experience this problem? none of
the xcode-users has ever heard of this?)
On Nov 12, 2005, at 11:14 AM, Dmitry Markman wrote:
try to build again:
if XCode complains just run build again and usually it will work
I saw that behavior in 2.1 as well
(and not only for java in native target too)
On Nov 11, 2005, at 8:28 PM, Nicholas Rinard wrote:
to me, correct me if I'm wrong, that indicates a bug in Xcode in
which Xcode does not add all the Compile Sources sources to the
javac argument.
i just created a brand new project and tried to move everything
into it. i set it all up and it looked good, and i compiled it.
this time, Xcode complained of a good couple dozen classes it
couldn't find. lo, the problem was the same: it complained that it
couldn't "find" about twenty classes which were at the bottom of
the Compile Sources list, and when i looked at the command line
argument, those files weren't in the list -- all the Compile
Sources were there down to a certain point, then the rest were
missing, and Xcode complained about all the missing classes.
maybe this whole problem is with my understanding of Xcode. i'm
going to go into naive mode an ask for some newbie help.
so... this is going to sound dumb... what do i have to do to get
Xcode to attempt to compile a class? apparently, evidently,
putting it in the Compile Sources list on a target isn't the right
way, because it doesn't work, reproducibly, so precisely what is
the mechanism for getting a class which is part of the project
into that command-line argument sent to javac?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden