Installare manualmente il wrapper Java
The installation package for the I2P router comes with a Java wrapper for the most common architectures. If your system is not supported by our installer—or if you want to update the wrapper to a newer version—the following steps describe installing the wrapper manually.
- Check Tanuki Software's download page for your platform. Is your platform listed? If so, you're in luck! Download the most recent version of the Community Edition for your OS and CPU and move to the next step.
- If your platform does not have an already compiled wrapper available, you may be able to compile it yourself. If you are willing to have a go at it, move on to compiling the wrapper for your system.
Usare il binari precompilati
In the steps below, $I2P means the location I2P was installed to.
tar xzf wrapper-*.tar.gz
cp wrapper*/bin/wrapper $I2P/i2psvc
cp wrapper*/lib/wrapper.jar $I2P/lib
cp wrapper*/lib/libwrapper.so $I2P/lib
- Try to start I2P using
$I2P/i2prouter start
tail -f /tmp/wrapper.log
and look for any problems.
If this did not work you'll need to use runplain.sh
to start I2P.
Compilare dai sorgenti
These steps worked to compile the wrapper for use on a mipsel system running Debian. The steps will need to be altered for your system.
- Download the source archive for the community version of the wrapper from wrapper download page.
- Estrai il tarball
tar xzf wrapper_3.5.13_src.tar.gz
- Set environment variables
ANT_HOME
andJAVA_HOME
. For example, in Debian:
export ANT_HOME=/usr/share/ant
export JAVA_HOME=/usr/lib/jvm/default-java
- Since there isn't a Makefile for Mipsel, we'll make a copy of an already existing makefile:
cp src/c/Makefile-linux-x86-32.make src/c/Makefile-linux-mipsel-32.make
- Now we can attempt to compile the wrapper:
./build32.sh
(use./build64.sh
if you have a 64bit CPU and JVM) - Copy the wrapper into its proper place:
cp bin/wrapper $I2P/i2psvc
cp lib/wrapper.jar $I2P/lib
cp lib/libwrapper.so $I2P/lib
- Try to start I2P using
$I2P/i2prouter start
tail -f /tmp/wrapper.log
and look for any problems.
If this did not work you'll need to use runplain.sh
to start I2P.