| Hello list,
I have run into a very odd problem building my application using Xcode 2.4/WO 5.3.x. Let me try to explain...
I am building an application with about 271 source files on the Application Server target. If I try to use the following command from a terminal window I get a build failure:
sudo xcodebuild install -configuration Deployment DSTROOT=/
I have determined the cause of the failure, but don't know how to fix it. The problem related to the following line from the build log:
/usr/bin/javac -J-Xms64m -J-XX:NewSize=4M -J-Dfile.encoding=UTF8 -extdirs /Library/WebObjects/Extensions:/Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Frameworks/JavaVM.framework/Home/lib/ext -g -encoding MACINTOSH -sourcepath /Users/robertwalker/Desktop/EMS/. -classpath "$classpath" -d "/Users/robertwalker/Desktop/EMS/build/EMS.build/Deployment/Application Server.build/JavaClasses" 'BusinessLogic/AbcClassification.java' 'BusinessLogic/AccountCode.java' 'BusinessLogic/Address.java' 'BusinessLogic/AS400Tractor.java' 'BusinessLogic/AS400Trailer.java' ...
I have shorted this line, hence the ellipsis at the end. The original command continued on to list 127 of my 271 source files. Yep you guessed it, the build obviously fails. I have double and triple checked my target settings and all 271 source files are included in the Application Server target just as they should be.
Here is the only workaround I have: Before using the command line to build the project I must first open and build the project using the "Deployment" build configuration from within Xcode. The project builds fine that way. Now, as long as I don't clean the files built by Xcode's build button, the command from the terminal works fine, but only because the object files have already been compiled from within Xcode.
I guess it's finally time to scrap Xcode for WO in favor of Eclipse. I've been dreading that, and putting it off, simply due to the fact that Xcode is "the devil I know." I stuck with it this long, because I was hoping not to have to get used to, and use, two different IDEs (one for Cocoa and one for WO). But it's screwball problems like this that may finally drive me there. -- Robert Walker
P.S. It's also driving me completely nuts not knowing the future of WO and WO tools. I know there's work being done in this area, but in the interim it's completely frustrating. Don't get me wrong, I'm excited about the prospects of what might come to pass, but that does nothing for me today.
I also loved the idea that I could install Xcode, check a checkbox in the installer, and I have a full set of tools configured and ready to go for WO development. I don't have confidence in the open source community providing a similar experience. It appears that it will always be more like, go here and download this IDE, then go here and download this plugin kit, then go here and get this tool, and go there and get that tool, etc., etc. Now you get to configure it all to work together, so have fun.... RoR is looking more interesting every day.
|