Re: address@hidden: Re: [GNU Crypto] new make plumbing]

[Raif S. Naffah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Sun, 28 Sep 2003 02:31 pm, Casey Marshall wrote:
> On Sun, Sep 28, 2003 at 01:54:28PM +1000, Raif S. Naffah wrote:
> > hello Casey,
> >
> > in the old days, i used to do the following for building a
> > non-gcj-friendly distro:
> >
> > address@hidden gnu-crypto]$ cd ../../build-no-gcj
> > address@hidden build-no-gcj]$ rm -rf *
> > address@hidden build-no-gcj]$ ../../workspace/cvs/gnu-crypto/init.sh
> > address@hidden build-no-gcj]$ ./configure --with-jikes
> > address@hidden build-no-gcj]$ make
> >
> > how can i have the same with the new mechanism?  doing
>
> You should set your CLASSPATH environment variable to reflect your
> system. The new Makefiles rely on environment variables, making them
> much more flexible.

sun recommends against using the CLASSPATH env variable 
(<http://java.sun.com/j2se/1.3/docs/tooldocs/win32/classpath.html>), 
and lots of projects avoid relying on it.


> With the old way it is not buildable, for example, with IBM's JDK,
> since it relys on a `rt.jar' file being the core class jar (it isn't
> always). Since it can be difficult to determine an appropriate
> CLASSPATH programmatically, I thought having a (rather simple) extra
> step would be an ok price for flexibility.
>
> A CLASSPATH of ${JRE_HOME}/jre/lib/{core,rt}.jar:. should suffice;
> maybe it would be a good addition to set a default CLASSPATH if it
> hasn't been explicitly set?

wouldn't that cause problems with jars that have to go in the 
bootclasspath?


cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE/dmdS+e1AKnsTRiERAzSLAJ4t4Q5QYQWS1n1Vy8nTjnt+vAh0nQCbBs3v
TnZSO5XyppjvzuuC0IVyXs0=
=bsA8
-----END PGP SIGNATURE-----