Re: XCode Link Error - What does this mean?
Re: XCode Link Error - What does this mean?
- Subject: Re: XCode Link Error - What does this mean?
- From: Chris Espinosa <email@hidden>
- Date: Mon, 5 May 2008 10:04:48 -0700
On May 5, 2008, at 9:58 AM, Rick Sustek wrote:
Marshall, et. al.,
Yeah, I hear you and get your points. Let me try to re-craft my
perspective in fewer words:
The fact that Apple used the UNIX, GNU, and OpenSource lever [to get
them and us to the state that the *entire system* is at today,] has
greatly accelerated what they have achieved, versus had they just
kept weaving new stuff into Mac OS "Classic". As developers, we do
need to be aware of this technology, and its pros and cons. And that
has everything to do with Xcode, and the problem of the original
poster. That lever is there for us to achieve greater work as well!
So, we file an enhancement bug report with Apple, and hope that they
can come up with a more elegant, integrated solution to file naming
quirks. Certainly, adding a short section in the "Files In a
Project" section of the Xcode User Guide, [that describes naming
conventions and restrictions,] would be a great start! ;-)
For myself, restrictions on file names is something I've been used
to dealing with for a way long time, and it bothers me not. But
progress in this area would be welcome!
This is simply a bug, not a deep philosophical issue or a culture war.
For makefile/command line purposes, gcc uses the -Wl,<option>
convention to pass through arguments to the linker when it is being
used as a linker driver. So commas are special-cased to detect that
usage. The compiler and linker ought not to co-opt the use of a comma
in a pathname in order to support that idiom.
Chris
_______________________________________________
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