Matthias Pfisterer wrote:
Dalibor Topic wrote:
My other problem is that libtritonusalsa needs javah
to run on some Alsa* inner classes. I can't seem to
get the $-character properly quoted in the Makefile.am
file, and I'm not even sure kaffe's javah properly
supports them anyway. If the inner
Dalibor Topic wrote:
--- Stuart Ballard [EMAIL PROTECTED] wrote:
Dalibor Topic wrote:
My current code fits it into kaffe's auto* tools
based
build as en extension library, adds a configure
option
for the sound backend to use, compiles the java
libraries, and links the C++ libraries
Dalibor Topic wrote:
--- Matthias Pfisterer [EMAIL PROTECTED]
wrote:
It is no longer necessary to build a library in
../common/. I'm now
linking the (single, small) object file to any
library in the other
directories. This is to simplify installation.
You could turn the helper functions in
Dalibor Topic wrote:
Hallo Matthias,
--- Matthias Pfisterer [EMAIL PROTECTED]
wrote:
My fix for this is to use libtool from current CVS and
upgrade out build scripts to latest auto* tools. There
are some issues in going that way, mainly increasing
the bar for build system developers, and
--- Matthias Pfisterer [EMAIL PROTECTED]
wrote:
Dalibor Topic wrote:
Hallo Matthias,
--- Matthias Pfisterer [EMAIL PROTECTED]
wrote:
My fix for this is to use libtool from current CVS
and
upgrade out build scripts to latest auto* tools.
There
are some issues in going that way,
--- Patrick Tullmann [EMAIL PROTECTED] wrote:
Hey Dalibor,
I didn't realize Tritonus provided part of JDK1.4
compatibility. I
see why you're trying to get it into the tree. Any
chance there is a
simple hacky fix to kaffe's libtool to get it to
link c++ correctly?
Maybe, I think I saw
Dalibor Topic wrote:
My current code fits it into kaffe's auto* tools based
build as en extension library, adds a configure option
for the sound backend to use, compiles the java
libraries, and links the C++ libraries accordingly.
Ouch, a configure option for the sound backend? Isn't that
--- Stuart Ballard [EMAIL PROTECTED] wrote:
Dalibor Topic wrote:
My current code fits it into kaffe's auto* tools
based
build as en extension library, adds a configure
option
for the sound backend to use, compiles the java
libraries, and links the C++ libraries
accordingly.
--- Dalibor Topic [EMAIL PROTECTED] wrote:
What I have at the moment, is that I've added
tritonus
to kaffe's build system, all the tritonus java libs
compile, the C++ libraries (except ALSA, because of
the inner class problems) compile and link,
SampleAudioPlayer starts but can't link
Dalibor wrote:
I'm trying to get kaffe's build system to work with autoconf 2.56
automake 1.7.1 as well as libtool from CVS. If all goes well, I hope
to have something to check in by the end of the week.
I'd be wary of upgrading the autoconf and configure requirements for
Kaffe, simply
Hi Pat,
--- Patrick Tullmann [EMAIL PROTECTED] wrote:
Dalibor wrote:
I'm trying to get kaffe's build system to work
with autoconf 2.56
automake 1.7.1 as well as libtool from CVS. If all
goes well, I hope
to have something to check in by the end of the
week.
I'd be wary of upgrading
Hey Dalibor,
I didn't realize Tritonus provided part of JDK1.4 compatibility. I
see why you're trying to get it into the tree. Any chance there is a
simple hacky fix to kaffe's libtool to get it to link c++ correctly?
We could wait until the *BSDs, Linux distributions and
the rest of the
12 matches
Mail list logo
