[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Java AWT for Debian?

At 17:17 02/06/2003 +0200, Arnaud Vandyck wrote:
José Luis Tallón <jltallon@adv-solutions.net> wrote:
> Hi all

>       Regarding      my     recently     packaged      "webCDwriter"     [
> http://wwwhomes.uni-bielefeld.de/jhaeger/webCDwriter/ ],  i have found
> *the* problem:  It needs AWT to  be compiled....  This has  not been a
> problem before, since upstream includes an already compiled and signed
> applet in JAR format... yet

The best practise is to build a package from sources.

It is only one of the binary packages ( architecture independent, obviously ) which contains Java. The rest is plain C++, which i build from sources *everytime*.

>   Now i have mostly solved every bug found during my own testing phase
> and repackaged it almost completely (  again! ) -- splitting it into 4
> subpackages from  the previous  2-- i must  solve the problem  that in
> won't compile in Debian ( Unless i make the webcdcreator a binary-only
> package -- sources  to the applet are available  in the source package
> nonetheless )

What are the errors? (You can maybe move this discussion on debian-java)

The "configure" script from upstream doesn't find the java compiler suitable ( which i can understand, given the lack of awt in my install )
( but see below )

> I tried with gcj-3.2 + libpja-java , to no avail
> Eclipse packages are currently br0ken in unstable

classpath  has some  java.awt  classes and  there  is a  jikes-classpath

Neither gcj-3.2 + classpath nor jikes + jikes-classpath worked

> The program was designed for jdk-1.4

So, why  not compile it with  j2sdk-1.4 (there is a  Debian package from
Blackdown[1]) and put your package in contrib?

It was already in contrib due to some "to be resolved" at the moment issues. Guess it has a good reason now.

Update: j2sdk1.4 from blackdown didn't do it, either :-(

The "offending" code ( in configure ) is this:
( I am not a Java programmer myself , BTW )

---- 8< ------------------------------

cat > Test0.java << EOF
class Test0 {
       static int foo { return 0; }

cat > Test.java << EOF
class Test {
        public static void main(String[] args) {
                new java.awt.Button();
                new javax.swing.JButton();

javac Test.java 2> /dev/null && webCDcreator="webCDcreator.jar"

---- 8< ------------------------------------

> Any suggestions as to how to make it compile?
> Shall   i   just   forget  about   it   and   let   it  be   just   an
> architecture-independent binary-only package  ( this implies including
> the upstream-precompiled JAR within the source package ) ?

This is a solution but I think  if you can not build it in Debian, there
are few chances to get it run in Debian! :-(

If j2dk1.4 --although non-free-- is accepted by the "contrib" autobuilders, it will certainly do.
I would have loved it to be in main, however :-|

> After reading the license at Sun's JDK download pages, i fully understand
> there is *no way* in which this license can be made compatible with DFSG
> and hence be packaged. Any alternatives?

http://classpath.org [2]  The package  is in Debian  and there  are some
wrapper for VM and compilers[3].

Didn't work :-|   Thanks for the pointer.

Best regards,

[1] http://blackdown.org/java-linux/mirrors.html

[2] http://www.gnu.org/software/classpath/

[3] see 'apt-cache search classpath'

-- Arnaud Vandyck, STE fi, ULg
   Formateur Cellule Programmation.


Debian-Java: Please CC me, since i'm not in that list

Reply to: