Apple

Chris--

You are right about everything you say.

The truth is that a lot of the people who want to come to try out Objective-C and Cocoa come from design and RoR backgrounds, and we are being told to use Macports to set up our environments (along with using Textmate, etc.) for development, and we are following instructions such as that laid out on:

http://www.buildingwebapps.com/articles/17-setting-up-rails-on-leopard-mac

to get ourselves started.

I would like to become better at Unix, but that is not my primary goal. It is just a means to an end for me. FYI, I come from a business background, not a programming background. My reason for learning programming is so that I can do things I have wanted to do by myself.

The best solution would be either:

1. For Apple to offer a recommended development environment which encompasses Objective-C, Cocoa and RoR which may or may not include Macports or Fink or;

2. Just tell those of us who come from business and/or non-Unix backgrounds that Apple is not interested in supporting us on your platform for development of business applications, in which case I will look for other platform solutions.

Paul Denlinger

On Sun, Jul 20, 2008 at 10:23 PM, Chris Espinosa <email@hidden> wrote:

On Jul 18, 2008, at 8:41 AM, Paul Denlinger wrote:

I'm working on my first Cocoa lesson at http://www.cocoadevcentral.com/d/learn_cocoa/

Everything works fine until I try to compile the app in Xcode 3.1. I get error code 71. Can you tell me what's wrong? Here is the error message:

error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings' (No such file or directory)

What we've established so far in this thread is that a) you have installed MacPorts, b) you don't know much about nuances of Unix, like shells, paths, or environment variables, and c) people who do know from Unix and have installed MacPorts are not seeing the problem.

I think it's only fair to point out that if you don't know much about Unix, you probably shouldn't install MacPorts.

Since MacPorts uses admin privileges to alter many crucial system directories in your root volume, reinstalling Xcode or switching to a different user will not allow you to escape its effects. Sadly the only thing to do is to reinstall Mac OS X and give it another try without installing MacPorts. Then if and when you do, be very careful about what you do and how you do it.

Chris

--
Paul Denlinger
"Risk is about seeing opportunities when others see challenges."
Skype: pdenlingercbs
Profile:http://www.linkedin.com/in/pauldenlinger
Visit my blog at www.chinavortex.com
China | Business | Economy | Internet|Technology

DISCLAIMER:
The content of this email and any attachment may contain proprietary and confidential information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then deleting it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.

References:
	>Problem compiling first Cocoa app in Xcode 3.1 (From: "Paul Denlinger" <email@hidden>)
	>Re: Problem compiling first Cocoa app in Xcode 3.1 (From: Chris Espinosa <email@hidden>)