Dirk Reiners wrote:
> Hi Patrick,
> Patrick Hartling wrote:
>> Tweek is optional depending on the availability of its dependencies.
>> If the JDK isn't available, then the Java components will be skipped.
>> If omniORB isn't available, then the C++ component will not be built.
>> Without Tweek, you won't get run-time reconfiguration or VRJConfig,
>> but it sounds as though you're OK with that.
> my problem is that I have a Java runtime, but not the javac compiler. With this
> configuration compilation stops when it tries to compile the java parts of tweek...
The configure script fails entirely? It shouldn't do that. The idea was that
failure to detect javac would mean that the JDK wasn't available. The logic
of the detection can get screwed up by environment variables and command
line options, however. This is what the test does to figure out if the JDK
1. Search path given on the command line (--with-jdkhome)
2. Search in the path(s) given as arguments to this macro (DPP_PATH_JAVA)
3. Search in $JDK_HOME (if it is set)
4. Search in the user's path
5. Search in a preset list of common locations
If you have JDK_HOME set to point at a JRE installation, that might be the
cause of the failure.
> I just installed the JDK to get around that for now, just FYI.
OK. Sorry for the headaches related to this. Cross-platform JDK detection is
hairy to say the least, and the detection tests haven't been updated in a
long, long time. There may be ways to simplify or improve them.
Patrick L. Hartling
Senior Software Engineer, Priority 5
The information transmitted in this communication is intended only for
the person or entity to which it is addressed and contains proprietary
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please destroy any copies, contact the sender
and delete the material from any computer.