1) Yes FindPackageHandleStandardArgs seems to handle that. I was looking eventually for some way to customize the error message...<br><br>2) I did not see the readme.txt, my bad... In this case, I think it is alright :-) (unless, other developers have comments...). I wanted to have only the path (not the full path with the executable name) for xjc compiler (which is installed in the same directory as java, javac, jar, etc. if I am not wrong). I think I will just do a get_filename_component on the Java_JAVA_EXECUTABLE.<br>
<br><br><div class="gmail_quote">2009/11/2 Mathieu Malaterre <span dir="ltr"><<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
'lo,<br>
<div class="im"><br>
On Mon, Nov 2, 2009 at 2:35 PM, Romain CHANU <<a href="mailto:romainchanu@gmail.com">romainchanu@gmail.com</a>> wrote:<br>
> Hello,<br>
><br>
> Regarding the FindJava.cmake, I have a couple of improvements to suggest:<br>
><br>
> 1) I have noticed that there is no JAVA_FOUND variable in the current<br>
> version (and your version).<br>
<br>
</div>I have not tested it, but it seems to me that<br>
FindPackageHandleStandardArgs.cmake is the one handling the setting of<br>
this variable IMHO.<br>
<div class="im"><br>
> 2) a JAVA_PATH (or another name) could also return the path where the Java<br>
> executables are located.<br>
<br>
</div>$ cat Modules/readme.txt<br>
...<br>
XXX_EXECUTABLE Where to find the XXX tool.<br>
XXX_YYY_EXECUTABLE Where to find the YYY tool that comes with XXX.<br>
...<br>
<br>
I decided to go for: Java_JAVA_EXECUTABLE / Java_JAVAC_EXECUTABLE/<br>
Java_JAR_EXECUTABLE. It make it easier to write in a foreach loop. I<br>
could leave them as such and add a Java_EXECUTABLE.<br>
<br>
Comments ?<br>
--<br>
<font color="#888888">Mathieu<br>
</font></blockquote></div><br>