Re: [GNU Crypto] Re: GCJ build

[Raif S. Naffah]

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

hello Olivier,

On Thursday 24 October 2002 22:31, Olivier LF wrote:
> On Wed, Oct 23, 2002 at 11:05:33PM +1000, Raif S. Naffah wrote:
> > that's a very good point! should we do the same for the top level
> > directory too?
>
> I'd say yes.

ok.  i'll add the Makfile.in to the cvs tree this weekend.


> > doesn't the user need to have LIBTOOL anyway to use the gcj/ tools?
> > doesn't including the Makefile.in as you point out in the previous
> > part of the message enough to address the needs for people who want
> > to just compile sources?
>
> ...
>
> The LIBTOOL step cannot be skiped otherwise the resulting Makefile
> has syntax errors in it.
>
> I can't remember the exact problem but from the top of my head you
> get something like that:
>
>
> Makefile.am includes the offending:
>
> lib_LTLIBRARIES = lib-gnu-crypto.la
> ...
> ...

are you saying that even if we put those lines inside a:

if USE_GCJ

lib_LTLIBRARIES = lib-gnu-crypto.la
...
...

endif #USE_GCJ

we still end up with a broken Makefile?


> At the time I gave up! Considering that Ant is so simple (and fast)
> to use, I decided it didn't worse the effort and time, and went on
> using Ant scripts for bytecode compilation and specific GCJ
> Makefile.am for GCJ native compilation.

worst case scenario: we already have the build trilogy (ant + 2*make); 
and they do the job.

best case scenario: we end up with ant + make, and less files and 
procedures to worry about when building.


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

iD8DBQE9uSb3+e1AKnsTRiERA5DUAKDc0bC54ohrmz6njSaosky1tr5T4ACeOcnz
QKtKBQz832dOHMeajp8FJLE=
=nq3z
-----END PGP SIGNATURE-----