On Thursday, July 06, 2006, at 01:50PM, Jerry <email@hidden> wrote:
>>> Actually XCode works fairly well for Java, but there are some big
>>> annoyances. The one which drives me completely crazy is that it can't
>>> parse javac error messages meaning that you have to read all your
>>> errors from the compiler text output.
>>
>> I've got this working by using an ant (external) build target.
>> There is an argument you must give to ant to make it not prepend
>> its own crud to the diagnostic messages (-emacs). I also use an
>> external build target for my JNI libs, using make. The JAM targets
>> suffered in the switch to XCode 2, so I try hard to avoid them.
>
>I'm already using the -emacs option. There are two problems: one is
>that XCode doesn'r parse the javac "cannot find symbol" message so
>that you have to hunt through the textual output to see what symbol
>is undefined.
You can get this info directly by looking at the raw build output. Click the little button that looks like text at the bottom of the built output in Xcode. (It's the third button.) I personally use the splitter to see both the parsed output and the raw output. Selecting a row in the parsed output also highlights the originating message in the raw output, so you get the best of both worlds.
>The other problem started just a couple of days ago -
>I'm guessing it was the 10.4.7 update. Now I often get Build Failed
>with no errors messages in the top pane and I have to read all the
>javac errors from the text output. This is really tedious as you
>can't click on an error to go to the line in the source file.
I've never seen that but if you look at the raw build output you are most likely going to see what is going on.
Steve
--
Steve Roy
<http://homepage.mac.com/sroy>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
