eID-Viewer is a graphical interface to the Belgian Electronic Identity Card use it to view, print, save data from the Belgian electronic identity card.
eID Middleware Project Copyright (C) 2010 - 2013 Fedict
By Frank Marien Based on eID Applet by Frank Cornelis
This is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License version 3.0 as published by the Free Software Foundation.
This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this software; if not, see http://www.gnu.org/licenses/.
Official releases and support are available on http://eid.belgium.be/. Source code and other files are available on http://code.google.com/p/eid-viewer/. Source code for eID Applet is available on http://code.google.com/p/eid-applet/
BUILD:
Requires a recent Maven installation, with dependencies. Tested only on GNU/Linux systems, but should work on any Maven-enabled system
$ mvn clean package
produces:
a shaded, runnable jar file in eid-viewer-gui/target: e.g. eid-viewer-gui/target/eid-viewer-gui-4.0.7.jar run with java -jar eid-viewer-gui/target/eid-viewer-gui-4.0.7.jar on many platforms, this jar can be ran directly, e.g. double-clicked or used as an executable.
a zipped OSX Application Bundle in eid-viewer-osx/target e.g. eid-viewer-osx/target/eid-viewer-osx-4.0.7-bundle.zip copy to an OSX system and unzipping will awake its bundle nature: It will become a runnable application. Double-click to run.
There are autoconf/automake files in the distribution root dir, to facilitate packaging/running on GNU/Linux systems. These assume the presence of the shaded jar described above. See comments in Makefile.am
In addition, if you have a local launch4j installation, add it as a property: e.g.
$ mvn -Dlaunch4j-base=/opt/launch4j clean package
.. this produces, additionally to the 2 artifacts described above,
(We used the launch4j maven plugin, in previous versions, eliminating the need for a local launch4j installation, but this plugin is unmaintained, while launch4j itself is alive and kicking. The resulting .exe was no longer fully functional. This compromise is slightly more difficult to build, but much better for the end-user).
EOF