Re: Build completes after touch
Re: Build completes after touch
- Subject: Re: Build completes after touch
- From: Godfrey DiGiorgi <email@hidden>
- Date: Fri, 5 Dec 2003 09:02:08 -0800
Greg's problem was fixed by the same workaround applied to John's:
setting the Build Style "GCC_Version" parameter in the Xcode native
target to a valid value ("3.3" in these cases). Xcode's native build
system is stricter about this than the Project Builder jambase build
system; "3.x" is not a valid value.
Thanks to both of you for reporting the problem and sending a project
to analyze.
Godfrey
---
Godfrey DiGiorgi - email@hidden
408 974-6814 tel - 408 974-8101 fax - 408 832-8319 cell
Technology Manager, Development Tools
Apple Worldwide Developer Relations
On Dec 5, 2003, at 8:42 AM, Greg Hurrell wrote:
I've already filed a bug for this one. I asked a question much like
this a couple of days ago, with the subject "Xcode compiles nothing on
target converted from classic to native".
Godfrey DiGiorgi, from Apple, told me that he had heard others report
similar issues, and so it might be an Xcode bug. Matthew Formica, also
from Apple, advised me that one way to fix it is to do what you
mentioned: creating a new target rather than upgrading.
Hopefully the issue will be fixed soon.
Best wishes,
Greg
El 04/12/2003, a las 23:43, John Ashley Burgoyne escribis:
Hello,
Please pardon me if this is a repeat question. The list archives are
not searchable yet, and no subject lines looked quite right when I
went through the archives by hand.
In several of my upgraded projects, native targets for applications
"complete" their builds successfully after only copying the resource
files. Instead of compiling the source files (or even invoking the
compiler at all), it touches the <APPNAME>.app directory and stops.
There are no warnings nor error message, and Xcode considers the
build successful. This happens both from within Xcode and using
xcodebuild from the command line.
Some projects have upgraded without this problem, others came around
after playing with creating new targets and re-adding the source
files, and in one project, the only way to fix it was to delete the
project and create a new one, re-importing each source file one by
one. I would *really* rather not do that again, but I'm dealing with
another project recalcitrant project.
Has anybody else had this problem? Is there a workaround? Does a bug
need to be filed?
Thanks in advance for any ideas,
J. Ashley Burgoyne
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.