[Debutant(e)]pb d'installation

j(ai pris le linux-motif.zip
en fait j'ai un autre problème.
1:après avoir installé celui ci,je l'ai dézippé dans la partie /home/sophie.
déja est ce que c'est une bonne idée? :oops:

2:ensuite j'ai changé le path du LD_LIBRARY,je l'ai mis dans le /home/sophie,est ce toujours une bonne idée?

3:enusite lorsque j'essaye de faire:

Citation:

---

/home/sophie/eclipse -data $HOME/workspace

---

et bien on me dit que /home/sophie/eclipse est un repertoire.
bon ma question est surement tres con,mais pourquoi je peux pas faire ça?




[Modéré par Didier]
Ajout de tag dans le titre
Lire les règles du forum : Règles du forum Java

alors,ya vraiment personne pour répondre à une question de débutante? :cry:

Je te la fais en anglais ça te fera les pieds... :lol:
si te mets à java va falloir parler anglais et chercher: sun la ref...

Getting Eclipse Running
=======================

This section makes the following assumptions: Your eclipse.zip is unpacked
into /opt/eclipse and your JDK resides in /usr/local/java/jdk1.3.1. The
assumed home directory will be /home/joe. We'll need that for the
workspace directory. The easiest way to run Eclipse is to call it from the
command line with a data switch, like this:

le must est de l'installer dans le repertoire opt

/opt/eclipse/eclipse -data /home/joe/workspace -ws motif
:idea:
ben alors? ya un executable ds le répertoire? :roll:

Some people reported that they avoided problems with the -ws switch. It is
not strictly necessary. It can be either 'motif' or 'gtk' for *nixes at
the moment. If you are seeing a splash screen, and, after a while, the
Eclipse workbench, you are done. Congratulations!



Usually Eclipse does not work so smoothly, and you may want to have more
control. Next step, specify a Java VM on which to run Eclipse, like this:


là c'est le 2ème effet kiss cool
/opt/eclipse/eclipse -data /home/joe/workspace -ws motif -vm
/usr/local/java/jdk1.3.1/bin/java

Note that the -vm switch needs the Java executable to be specified. The
path to the JDK like in $JAVA_HOME or even to the bin directory is not
sufficient. On the command line this should be working very often. You
should now be seeing the splash screen and, after a while, the Eclipse
workbench. Congratulations!



One person, trying to get Eclipse running on a BSD flavor, reported that
Eclipse could not find the swt-motif-2026.so library. This library serves
as a bridge between SWT (the Eclipse windowing) and the native windowing,
i.e. the windowing widget set used by your OS. Can be Motif, GTK, or
(rumored) KDE/Qt on Linux. In order to find the correct library specify
the -arch switch, short hand for architecture, like this:

/opt/eclipse/eclipse -vm /usr/local/java/jdk1.3.1/bin/java -data
/home/user/workspace -ws motif -arch x86

If the above does not work, you may try specifying the library directly,
with the -vmargs switch. Note, that the path may change in future
releases. Still, as a last-ditch-effort it may do the trick, like this:

/opt/eclipse/eclipse -vm /usr/local/java/jdk1.3.1/bin/java -data
/home/user/workspace -ws motif -vmargs
-Djava.library.path=/opt/eclipse/plugins/org.eclipse.swt/ws/motif

Note that everything has to be written on one line. Also note that the
parameter for java.library.path only needs the path to the xxxx.so
library/file, not the file itself. You can use this switch to specify
other native libraries you may need. Also note that the -vmargs switch has
to be last with its parameters. Hit enter, and you should be seeing a
splash screen and after a while the Eclipse workbench. Congratulations!


8O
Some additional comments about windowing. Eclipse in its current motif
version (see changelog for exact version) is known not to work with
Lesstif, which is the Motif on RedHat Linux 7.2. To use the Motif version
on RedHat Linux 7.2 set the LD_LIBRARY_PATH environment variable. This
will force Eclipse to use its own Motif library, which it is carrying with
it. There are various ways of setting *nix environment varibles. You may
do it like this:

On RedHat 7.2 with bash shell, for starting Eclipse from the command line:
export LD_LIBRARY_PATH=/opt/eclipse:$LD_LIBRARY_PATH

On RedHat 7.2 with bash shell, for starting Eclipse from a desktop icon:
Open .bash_profile in your home directory and insert the following two
lines:
LD_LIBRARY_PATH=/opt/eclipse:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Save .bash_profile, log out of your current user account, and log on
again. You should be able now to launch Eclipse from a desktop icon.

On any other *nix system with a C-Shell like csh or tcsh, on the command
line:
setenv LD_LIBRARY_PATH /opt/eclipse:$LD_LIBRARY_PATH



There are other parameters that you may want to control when launching
Eclipse such as heap and stack size. Use the -vmargs switch like this:

/opt/eclipse/eclipse -vm /usr/local/java/jdk1.3.1/bin/java -data
/home/user/workspace -ws motif -vmargs -Xms50m -Xmx100m -Xss20m

If you want to control still more options, launch Eclipse as a regular
Java application, like this:

/usr/local/java/jdk1.3.1/bin/java -Xms100m -Xmx200m -verify -cp
/path/to/eclipse/startup.jar org.eclipse.core.launcher.Main -data
/home/joe/workspace -ws motif

All on one line.



Check my Java
=============

Before reporting problems, it's probably a good idea to try (on the
command line) running Java first. The easiest test simple asks for the
Java version, like this:

/usr/local/java/jdk1.3.1/bin/java -version

If you get a response, then, at least, you know that Java is not seriously
broken. Another, more demanding test is compiling and running the program
below. Compile like this:

javac HelloWorldSwing.java

Run like this:

java HelloWorldSwing

A little dialog should appear in the upper left corner of your desktop
saying 'Hello World'. Now you know that Java works, mostly. This is the
program, save in file HelloWorldSwing.java:

import javax.swing.*;
public class HelloWorldSwing {
public static void main(String[] args) {
JFrame frame = new JFrame("HelloWorldSwing");
final JLabel label = new JLabel("Hello World");
frame.getContentPane().add(label);

frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.pack();
frame.setVisible(true);
}
}

a+ 8) keep cool et pense à GOOGLE!!!!!!!!! donne de tes news...

ecoute,je te fais de gros bisous,c'est super cool de ta part.
je n'ai pu trouver de la doc pour le 3.0 mais je dois dire que j'ai afit d'autres choses entretemps.
je vais m'emploeyr à faire marcher tout ça tres vite parceque j'ai hate de faire tourner tout ça.

encore merci à toi.gros bisous. :calin:

:o oh! un peu d'amour dans ce monde cruel du dev...
j' en reste confus... :oops:
Mais pense au tag [RESOLU] en bas à gauche :twisted: !!

a+ 8) learn to search!