Daniel Rall wrote:
> Justin Erenkrantz wrote:
...
>> Well, the problem I have is that I really dislike hardcoding the
>> JRE_LIB_DIR. If we could find a way to determine this from having the
>> JDK in /Library/Java/ or something, I'd be more comfortable. But, the
>> degree to which we're hardcoding paths is getting uncomfortable. --
>> justin
>
> Justin, I've never heard of any way to programmatically determine this
> information. (Doesn't mean there isn't one, of course.) I don't see
> this as a significant issue, though, since the highest percentage of
> people compiling Subversion will be using the JDK from Sun (or Apple, if
> on OS X ;). General path structure for the JDK's of these vendors tend
> not to vary much across versions. Sun's JDK always includes a JRE at a
> specific location relative to the root of that JDK, making this
> something of a non-issue from the get-go. Apple doesn't seem to follow
> this structure, but is likely to always install the JRE in the same
> place anyhow. If you hear of any OS X-foo for requesting the location
> of the JRE, let me know and I'll add that logic to java.m4.
>
> That said, does that patch look like it will fix the immediate problem?
> Like I said, I'm not up and running on moof yet. Did you have a chance
> to try it out?
Another option is the addition of a --with-jre configure flag which overrides
the default, (for Sun, semi-)hard-coded paths, allowing building by users with
irregular installations.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 30 05:49:05 2004