Source code compilation (Windows)
To compile Evernus on Windows, you’ll need Visual Studio 2017. Make sure you have all the prerequisites downloaded. Assuming you installed Qt to c:\Qt and Boost to c:\Boost, you have to invoke cmake to generate Visual Studio solution from VS command prompt, like so:
cmake -G "Visual Studio 15 2017 Win64" -DCMAKE_PREFIX_PATH=c:/Qt/5.11/msvc2017_64/lib/cmake -DBOOST_ROOT=c:/Boost
Then just hit F7 and you’re good to go!
Source code compilation (Linux)
Before starting to compile the code, make sure you have installed all the prerequisites. The following manual assumes you have clang set as your c++ compiler, all the required libraries available in the system and Qt installed via their installer in your home directory.
First you have to generate a Makefile. This is done by invoking the cmake tool. If you don’t know what cmake is, you can read about it here. The simplest way is by using the console. For example, let’s assume you downloaded Qt 5.11 prebuilt with gcc:
cmake -G "Unix Makefiles" -DCMAKE_PREFIX_PATH=/home/$USER/Qt/5.11/gcc_64/lib/cmake
This will generate a Makefile for use with make (assuming no errors). Note, that this is a step you should be doing just once. The only thing left to do is:
make
And that’s it! Evernus should compile without errors. The resulting binary MUST reside in the same directory where the res/ and trans/ subdirectories are located, otherwise Evernus won’t be able to open Eve database and translations.
Source code compilation (OS X)
Before starting to compile the code, make sure you have installed all the prerequisites. For creating your own OS X bundle you have to build Qt frameworks which will be later imported into the app. You can do that by giving -framework to Qt configure command (remember to apply required patch to QXmlPatterns):
./configure -opensource -confirm-license -framework -prefix $PWD/qtbuildframeworks -nomake tests -nomake examples -release -skip qtwebkit
You can also see couple of additional options here:
-prefix $PWD/qtbuildframeworks
will help us to gather all frameworks and required files in one place.
-skip qtwebkit
this will skip WebKit compilation which is a rather long process.
Once you are done configuring you can compile with make and install Qt to set prefix with make install. Once you are done with Qt you can start building Evernus. First you have to generate a Xcode project. This is done by invoking the cmake tool. If you don’t know what cmake is, you can read about it here. The simplest way is by using the console. For CMAKE_PREFIX_PATH you need to use the path you have provided to -prefix option of Qt configuration. Let’s assume you have downloaded Qt 5.11 sources and used configuration command above.
cmake -G "Xcode" -DCMAKE_PREFIX_PATH=/Users/$USER/Downloads/qt-everywhere-opensource-src-5.11/qtbuildframeworks
This will generate an Xcode project file inside Evernus source directory.
The last step is to compile and bundle the application. You can compile with:
xcodebuild -project Evernus.xcodeproj
Don’t mind the errors given from Xcode – it should compile properly; this is because Xcode cannot parse multiline strings. And finally bundle with:
xcodebuild -project Evernus.xcodeproj -target install
Remember about the last command because as the app bundle is created with previous command, all the dependencies are moved into the bundle in this step. And you are ready to go!
Source code compilation (all)
If you want Eve ESI or Dropbox support, you need to register your application on their respective developer webpages.
Eve SSO client id/secret has to be specified as constants/defines for cmake in order to work. These are:
- EVERNUS_CLIENT_ID/EVERNUS_CLIENT_SECRET – SSO client id/secret
The callback is https://evernus.com/sso-authentication/
Dropbox id/key are similar:
- EVERNUS_DROPBOX_APP_KEY/EVERNUS_DROPBOX_APP_SECRET – Dropbox app key/secret
The should be given (usually only once) as arguments for cmake:
cmake -DEVERNUS_CLIENT_ID=id -DEVERNUS_CLIENT_SECRET=secret -DEVERNUS_DROPBOX_APP_KEY=key -DEVERNUS_DROPBOX_APP_SECRET=secret
If you don’t want to use Google Breakpad, you can turn this off from cmake:
cmake -DEVERNUS_CREATE_DUMPS=OFF
Docker
Evernus comes with Dockerfile which you can use to build and run the application. Note – depending on your host system, you might need to forward some devices to make rendering work.
You can use the official Docker image: krojew/evernus – see the description for details.
Restoring database backup
Update process creates a database backup, which can be restored in case something goes wrong. You can find it in the c:\Users\your_user\AppData\Local\evernus.com\Evernus\db directory on Windows, or ~/.local/share/evernus.com/Evernus/db on Linux, named main.db.bak. Simply rename it to main.db and the backup will be restored.