Re: XCode 2.1: Custom projects
Re: XCode 2.1: Custom projects
- Subject: Re: XCode 2.1: Custom projects
- From: James Bucanek <email@hidden>
- Date: Sat, 26 Nov 2005 12:28:27 -0700
Franco Milicchio wrote on Friday, November 25, 2005:
>Ok, I imagined that. I'd like to do something more :)
>
>I'd like to write the build rule and use as many XCode features I see
>in C projects:
>
>- Groups
You can already use source groups and organize your files however you want.
>- Products
I don't see how products would be applicable here. You certainly don't want the output of each source file to be a product. A target produces, at most, one product so this would require one target for every source file. I'm sure that's not what you were thinking.
A copy files or run script phase should be able to gather the results of your compilations together and aggregate them into a single output location. It wouldn't show up as a product in the project, but it would be equivalent.
>- Targets
You can already use and organize targets however you want. You can put source files into whatever targets you wish and make target dependencies. The build-rules suggestion I already made is completely built around existing targets. I can't imagine any features of Targets that you can't exploit now.
>- Errors and Warnings
>- ...
>
>Basically create the entire framework I use in C projects (latex
>output parsing like xcode's gcc parser). It would be nice to see also
>symbols per file (as in C) and project symbols list.
These I don't think you can do any of these without writing a plug-in for Xcode. My understanding is that each language/target-type supported in Xcode works through a plug-in that translates the specifics for that language, identifies error messages in the build logs, and communicates a myriad of other details to the Xcode application. Xcode plug-ins are not documented and doubt anyone outside of Apple could write one.
However, this request has come up before. You might contact ADC and ask, or file an enhancement request for an Xcode plug-in SDK so that Xcode could be expanded by third parties to support other languages.
>A tex/latex project is not so different from a c one except that you
>don't execute the output :)
Again, I have to say that since a lot of Xcode is focused on producing, running, and debugging executable output there will always be a large number of Xcode features that won't be applicable to a document production environment.
James
P.S. Have you considered Eclipse + Ant as a solution?
--
James Bucanek
_______________________________________________
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