p≡p engine FORK
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Volker Birk 53ff6f7562 dicts for en and de 7 years ago
build-android Android : build script now needs GPGME_INCLUDE_PATH env var to be set. 7 years ago
build-mac Added explicit linking to etpan and pEpEngine static libs 7 years ago
db dicts for en and de 7 years ago
src rating for decrypt() corrected 7 years ago
test Fixed unittests on Linux 7 years ago
.hgignore Moved android -> build-android. Updated .hgignore. 7 years ago
LICENSE.txt should be there 8 years ago
Makefile even nicer 8 years ago
Makefile.conf decoding body correctly 8 years ago
README.txt message api 8 years ago
TODO.txt case conversion including tailoring based on PyICU 8 years ago
pEpEngine.vcxproj release build 7 years ago
pEpEngine.vcxproj.filters modifications for Windoze 8 years ago

README.txt

pEp Engine
==========

0. What it is and building it
-----------------------------

The pEp Engine encapsulates all real functionality of pEp.
It has an old style Makefile for building it.

The build is configured in Makefile.conf

It supports the common targets

$ make all
$ make install
$ make clean

and additionally

$ make package # for building a .tar.bz2 with the source distribution

To build on platforms without uname(1) use BUILD_ON:

C:\pEpEngine> :for building a .zip with a binary distribution
C:\pEpEngine> set BUILD_ON=Windoze && make -e windist

1. How to cross-build
---------------------

For cross-building, BUILD_FOR is being used. I.e.:

$ BUILD_FOR=Windoze make -e windist

Supported platforms are Darwin, Windoze, Linux.

1. a) Cross-building for Windoze
................................

Cross-building for Windoze requires mingw-w64.

Easier linking to Visual Studio can be achieved by using Microsoft's LIB.EXE
tool; this command created the needed pEpEngine.lib import library:

C:\pEpEngine> lib /def:pEpEngine.def

2. How to build the databases
-----------------------------

pEp Engine uses two databases: ~/.pEp_management (on *NIX) or
%LOCALAPPDATA%\pEp\management.db on Windoze respectively, and
/usr/local/share/system.db on *NIX or %ALLUSERSPROFILE%\pEp\system.db
respectively. The latter contains the safewords dbs.

The managment db is being created by the first call of init() of pEp Engine. It
does not need to be created manually. system.db is being created by using the
DDL in db/create_system_db.sql – the content is created by db/dic2csv.py
out of hunspell's dictionary packages (or something similar) and then being
imported using sqlite3's .import command.

You can test the safewords in system.db using db/safewords.py
Both Python tools have a switch --help