[CMake] CMAKE_Java_LINK_EXECUTABLE

2006-07-31 Thread Richard Fuchs
I'm getting this error CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_Java_LINK_EXECUTABLE where/how does this variable get set? Thanks Richard ___ CMake mailing list CMak

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-01 Thread Brad King
Richard Fuchs wrote: > I'm getting this error > > CMake Error: Error required internal CMake variable not set, cmake may > be not be built correctly. > Missing variable is: > CMAKE_Java_LINK_EXECUTABLE > > where/how does this variable get set? What is your CMakeLists.txt file code that causes th

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-01 Thread Richard Fuchs
Brad King wrote: Richard Fuchs wrote: I'm getting this error CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_Java_LINK_EXECUTABLE where/how does this variable get set? What is your CMakeLists.txt file code t

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-01 Thread Richard Fuchs
To answer my own question, yes don't call ADD_EXECUTABLE with java files, use ADD_LIBRARY. After hunting through CMakeJavaInformation.cmake, it doesn't seem to have a CMAKE_Java_LINK_EXECUTABLE target/property (or whatever the correct name for it is). Does this mean that you can't call ADD_E

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-01 Thread Brad King
Richard Fuchs wrote: > After hunting through CMakeJavaInformation.cmake, it doesn't seem to > have a CMAKE_Java_LINK_EXECUTABLE target/property (or whatever the > correct name for it is). Does this mean that you can't call > ADD_EXECUTABLE with java files and I need to use ADD_LIBRARY or > somethi

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-02 Thread Richard Fuchs
Brad King wrote: Richard Fuchs wrote: After hunting through CMakeJavaInformation.cmake, it doesn't seem to have a CMAKE_Java_LINK_EXECUTABLE target/property (or whatever the correct name for it is). Does this mean that you can't call ADD_EXECUTABLE with java files and I need to use ADD_LIBRA

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-02 Thread Brad King
Richard Fuchs wrote: > So why when I have a simple CMakeLists.txt file like below am I getting > this error? Why is it trying to put the .class files in some funky > directory instead of just where the .java files are? Is there a way to > set the OBJECT_DIR that's in the CMakeJavaInformation.cmak

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-02 Thread Richard Fuchs
Brad King wrote: Richard Fuchs wrote: So why when I have a simple CMakeLists.txt file like below am I getting this error? Why is it trying to put the .class files in some funky directory instead of just where the .java files are? Is there a way to set the OBJECT_DIR that's in the CMakeJavaI

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-02 Thread Richard Fuchs
Spoke to soon, it seems to be a problem with where javac is invoked. With the current makefiles that are created, the javac -d option has a relative path from where the source files are located, but javac is being invoked from the root project dir. I was able to modify the build.make file tha

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-02 Thread Brad King
Richard Fuchs wrote: > Spoke to soon, it seems to be a problem with where javac is invoked. > With the current makefiles that are created, the javac -d option has a > relative path from where the source files are located, but javac is > being invoked from the root project dir. I was able to modif

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-03 Thread Richard Fuchs
Brad King wrote: Richard Fuchs wrote: Spoke to soon, it seems to be a problem with where javac is invoked. With the current makefiles that are created, the javac -d option has a relative path from where the source files are located, but javac is being invoked from the root project dir. I wa

Re: [CMake] CMAKE_Java_LINK_EXECUTABLE

2006-08-03 Thread Brad King
Richard Fuchs wrote: Brad King wrote: Richard Fuchs wrote: Spoke to soon, it seems to be a problem with where javac is invoked. With the current makefiles that are created, the javac -d option has a relative path from where the source files are located, but javac is being invoked from the