On Jul 19, 2012, at 7:51 AM, Joe Armstrong wrote: On Thu, Jul 19, 2012 at 4:36 PM, Glenn L. Austin <email@hidden> wrote:
On Jul 19, 2012, at 6:30 AM, Joe Armstrong wrote:
On Thu, Jul 19, 2012 at 2:32 PM, Roland King <email@hidden> wrote:
Doesn't work quite like that. You really wouldn't want Xcode stuffing random development code in /usr/local/bin every time you built it now would you. Xcode keeps all the built product in wonderfully segregated directories, segregated by platform, debug and release etc etc. So when you build a debug version of your app, it doesn't go stomp on the release one you built last month.
If you look at the build log (it's one of the tabs on the organizer), it's quite easy to find where it built what it ran in your debug session, for instance I have a PNG splitter, I just looked, it's here
I'm sorry I can't find a build log in the organiser. I opened the organiser by clicking on a little button that looks like a filing cabinet in the top right hand corner of the xcode screen
a thing called organiser opens. It has 5 icons on the top bar calleddevices, repositories,projects archives and documentation.
I searched for "build log" in the xcode help - it returned 27 system guides 9 tools guide and 26 entries in sample code - but sadly I still can't find this information.
The guide "Building and running apps" talks about the "base SDK" and their is an illustration referring to ioS4.3 - in fact the documentation at this point never
mentions Mac os x - strange since I'm developing on mac os x for mac os x and have no interest in ioS. The entire "Building and running apps" seems to be write from the POV that I'm developing for an
ipad or iPhone - but I'm not.
Xcode is like almost every other system, following a variation of the "configure/make/make install" steps, only in this case it will be Archive, go to the Archives tab in the Organizer, click on the archive that was created, click on the Distribute button and save the built products. That will create a directory with the resulting files relative to that path. Tar and untar as necessary.
It did - thank you
Glad to help! Or you can use the xcodebuild command-line tool to build and install, just xcodebuild build install. Add a clean before build and you'll get a completely rebuilt install (similar to "configure/make clean/make/make install").
OOhhh - I have no idea what I'm doing but I when to my project directory (the one that has a test1.xcodeproj file) and typed xcodebuild - this gave a lot of output and made a diredctory
called Build with my compiled program in it.
This seems to work.
Now I just need to figure out how to do the GUI bit from emacs :-)
There are a LOT of options to xcodebuild -- just look at the man page for the thing.
While it does require an xcodeproj file, that is not much different than requiring a make file -- and it's far easier to manage. I'm a UNIX guy from many years ago, and while I'm not afraid of configure/make clean/make/make install, Xcode makes managing my build targets, adding custom scripting steps, and building for multiple architectures so incredibly easy in comparison with make that there's really no comparison.
There's very little that I can do with make that I can't do with Xcode, although the methods are sometimes a bit more obscure than I would like.
-- Glenn L. Austin, Computer Wizard and Race Car Driver <><
"Where there's breath, there's hope!"
|