From simon.urbanek at math.uni-augsburg.de  Wed Dec 29 20:47:31 2004
From: simon.urbanek at math.uni-augsburg.de (Simon Urbanek)
Date: Wed Dec 29 20:47:17 2004
Subject: [Rd] Makefile vs Makevars vs configure
In-Reply-To: <7669F018DC9DD711AEC500065B3D5ABF042B3E2E@tudor.com>
References: <7669F018DC9DD711AEC500065B3D5ABF042B3E2E@tudor.com>
Message-ID: <7A815FC7-59D2-11D9-9BAC-000D93AE1C66@math.uni-augsburg.de>

On Dec 29, 2004, at 2:06 PM, Whit Armstrong wrote:

> The reason I need help with Makevars is because it needs jni.h from the
> user's JAVA_HOME/include and jni_md.h from the user's
> JAVA_HOME/include/OS_TYPE directory.
>
> In addition, it needs libjvm.so from the user's
> JAVA_HOME/jre/lib/ARCH/client directory.
>
> I've looked at the SJava package with the idea of using a similar 
> configure
> script, but I was hoping I could just get by with a Makevars file 
> rather
> than a configure script.

That is virtually impossible unless you let the user add all paths 
manually. Each OS, platform, VM vendor and VM version(!) use different 
paths and you need different include directories and libs. What you end 
up doing in your Makefile is what the configure script does, so I see 
no benefit from not using it. AFAIR SJava doesn't detect Apple Java - 
you may have a look at rJava's configure script which tries to be a bit 
more general, but your mileage may vary.

Cheers,
Simon


[Rd] Makefile vs Makevars vs configure
Simon Urbanek