Artkast:: Tips for using vi instead of ten code's text editor. [Changes]   [Calendar]   [Search]   [Index]   

Tips for using vi instead of ten code's text editor.

After learning how to use a superior editor such as vi it is really hard to go back to the pointy clicky style of textedit and whatever other dozens there are. Anyway I am trying to put together a listing of tips and tricks for building cocoa applications with vi or maybe emacs hmm nah. Alright maybe emacs too but there are already a bunch, anyway maybe I can get something good started.

Edit: I wanted to state that I was very sleepy when making this page, I really do like ten code or Xcode :) and really enjoy the pointy clicky style sometimes I have to say pragma marks are slick "pragma mark - " thanks to my friend matt for reminding me of that, is an especially nice little feature, I guess I get bored really easy and just like to change every minute or so. Anyway I then went to find tips and there were not many so I decided to compile this. Ok that's all.

==== SITES ====

Info on how to build your xcode projects command line style

=== TIPS ===

[ Sorry, all guestbooks disabled temporarily due to rampant spam :(   ]

=== What to do ===

I broke things down for impatient people like myself:

Building from the Command Line

1. use xcodebuild to build a target from the command line.

Building from the command line gives you additional flexibility (and less headaches) compared to building from within the Xcode IDE.
When you build from the command line, xcodebuild uses the first target in the project’s target list and no build style, unless you specify a target or build style with a command-line option.

2. running xcodebuild as the root user = preferences you set in the Xcode Preferences window are not used.
Preferences are stored per user, and there are no preferences stored for the root user (unless you logged in as root and used Xcode at some point).

3. To build a target using xcodebuild , use the cd command to change to your project’s directory and enter the xcodebuild command with any command-line options you wish to specify.
The project’s directory contains your project’s .xcode file.
For example, if your project is in ~me/Projects/MyProj , enter cd ~me/Projects/MyProj.

To build a product suited for deployment and install the product in its final destination path.

1. use the xcodebuild tool with the install option, which places the product in the distribution root specified by the DSTROOT, Installation Path (INSTALL_PATH), and Deployment Location (DEPLOYMENT_LOCATION) build settings.

To install a framework in /Library/Frameworks, configure the build settings as shown below.

[ Build setting name ]--------------------[ Value ]
[ DSTROOT ]--------------------------------[ / ]
[ INSTALL_PATH ]----------------------------[ $(LOCAL_LIBRARY_DIR)/Frameworks ]
[ DEPLOYMENT_LOCATION ]-------------------[ YES ]

The DSTROOT build setting can be set only in the xcodebuild command-line specification: % sudo xcodebuild install -buildstyle Deployment DSTROOT=/ INSTALL_PATH=/Library/Frameworks DEPLOYMENT_LOCATION=YES

See the xcodebuild man page for information on the available options and command usage. For details on framework placement, see “Frameworks” in System Overview.

Note: this was all borrowed from apple's page

I decided browsing to the project directory in terminal and having xcode show hierarchy works pretty well for me. Atleast I can see the heirarchy I am working with at the same time as I work.

(last modified 2005-03-08)       [Login]

( no categories on this page )

(No back references.)