• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode command line build with large Java projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode command line build with large Java projects


  • Subject: Re: Xcode command line build with large Java projects
  • From: David Ewing <email@hidden>
  • Date: Thu, 4 Dec 2003 14:21:01 -0700

What's going on is that when you're building in the IDE you have an index present. It looks like this isn't true for your command line builds. (Xcode, and PB before it, use the index to compute build dependencies. When this is done, it's also able to use the @JavaFileList feature of javac.)

To work around this, probably the easiest thing to do is to set the JAVA_SOURCE_PATH to a colon-separated list of project-relative (or absolute) paths of your source tree(s). This requires that you organize your sources in directory hierarchies based on their package names. (You can have multiple source trees - the root directories are what need to be listed in the build setting.) This setting lets javac find other source files that aren't explicitly listed on the command lines.

Dave

On Dec 2, 2003, at 3:56 PM, Michael Hast wrote:

We converted out existing PB Java WebObjects applications to Xcode. In order to release our products we run a release build script from the command line using xcodebuild. We are getting errors when large applications are being build (hundreds of java files). The errors are that some classes in the project cannot be found. However, building the application from within Xcode succeeds. Is that a known bug? Does anyone know of a workaround?

The build output from within Xcode and from the command line are different. From within Xcode a java file list is generated and passed to the java compiler (see below). From the command line, every java file is passed to the java compiler (see below). That results in an incomplete list and that causes the errors.

Build output from within Xcode:
/usr/bin/javac <arguments> '@/some/path/test.build/Application Server.build/JavaFileList'


Build output from command line:
/usr/bin/javac <arguments> 'Class1.java' 'Class2.java' ...

Again for small projects this is not a problem. But for hundreds of java files this is an issue.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Xcode command line build with large Java projects
      • From: Francis Labrie <email@hidden>
References: 
 >Xcode command line build with large Java projects (From: Michael Hast <email@hidden>)

  • Prev by Date: Application bound Frameworks
  • Next by Date: Re: XCode multithreaded?
  • Previous by thread: Xcode command line build with large Java projects
  • Next by thread: Re: Xcode command line build with large Java projects
  • Index(es):
    • Date
    • Thread