loot/libloot
0
0
Fork 0
mirror of https://github.com/loot/libloot.git synced 2026-07-27 14:16:01 -07:00
Code Issues Packages Projects Releases Wiki Activity

Update to CEF 3.2704.1427.g95055fe

Browse Source 
This CEF is based on Chromium 51, which drops support for Windows
Vista.

CEF now has builds hosted by Spotify that can be downloaded
automatically, so the build process has been updated to automate
downloading and building the CEF dependency. The version of CMake
in Ubuntu 12.04 doesn't support the URL_HASH parameter, so use a
more recent version from a PPA.

Unfortunately the minimal build's CMake config is broken
(https://bitbucket.org/chromiumembedded/cef/issues/1921) so for now
LOOT downloads the standard build (which is a much larger download).
This commit is contained in:
Oliver Hamlet
2016-06-12 14:06:40 +01:00
parent 353435a9e4
commit 549020e54c
9 changed files with 74 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BUILD.LINUX.md
+16 -14
View File
@@ -1,13 +1,15 @@
# Build Instructions using GCC
Linux binaries can be built for LOOT, and these instructions are for doing so on
Ubuntu Desktop 14.04, though they may also apply to other versions and
Ubuntu 12.04, though they may also apply to other versions and
distributions.
## Building
Most of the procedure for building the API, tests and metadata validator can be
found in the `.travis.yml` file, which is the configuration file for LOOT's
Travis CI instance. However, Travis instances have a few more libraries and
utilities by default than Ubuntu Desktop 14.04 does, and the procedure does not
utilities by default than Ubuntu 12.04 does, and the procedure does not
cover building the GUI application, so these differences will be covered here.
Linux builds of the GUI application should be considered officially
@@ -15,29 +17,29 @@ Linux builds of the GUI application should be considered officially
## Installing Missing Dependencies
To install Node.js (for building the HTML UI) and the libcurl and X11
development libraries (for libgit2 and the UI respectively), run the following:
### Base Dependencies
```
sudo apt-get install python-software-properties git build-essential libcurl4-openssl-dev
```
### UI Dependencies
```
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 68576280
sudo apt-add-repository 'deb https://deb.nodesource.com/node_4.x precise main'
sudo apt-get update
sudo apt-get install nodejs npm libcurl4-openssl-dev libx11-dev
sudo ln -s /usr/bin/nodejs /usr/bin/node
sudo npm install -g bower vulcanize@0.7.11
sudo apt-get install nodejs libx11-dev libgtk2.0-dev libnss3-dev libgconf2-dev libxss-dev libasound2-dev libxtst-dev
```
If you wish to build the GUI application, you must also manually download the
Chromium Embedded Framework binary archive, then extract it and run
## Pre-built Boost Packages Workaround
The pre-built Boost packages for Boost 1.55 and below in Ubuntu were built without C++11 support, which causes an error when linking with a C++11-built LOOT binary. While it's better to use a build of Boost with C++11 support when building LOOT, the error can be worked around by running the following before running CMake:
```
mkdir build && cd build
cmake ..
make
export TRAVIS=1
```
from the extracted folder.
## Runtime Differences
Not all LOOT's features have been implemented for Linux builds. Issues labelled
docs/BUILD.MSVC.md
-13
View File
@@ -11,19 +11,6 @@ b2 toolset=msvc threadapi=win32 link=static runtime-link=static variant=release
`link`, `runtime-link` and `address-model` can all be modified if shared linking or 64 bit builds are desired. LOOT uses statically-linked Boost libraries by default: to change this, edit [CMakeLists.txt](../CMakeLists.txt).
#### Chromium Embedded Framework
Most of the required binaries are pre-built, but the libcef_dll_wrapper dynamic library must be built.
1. Configure CMake and generate a build system for Visual Studio by running:
```
mkdir build && cd build
cmake.exe .. -G "Visual Studio 14"
```
2. Open the generated solution file, and build it with `Release` configuration.
#### LOOT
1. Set CMake up so that it builds the binaries in the `build` subdirectory of the LOOT folder.
docs/LOOT Readme.html
+1 -1
View File
@@ -226,7 +226,7 @@ figure > div {
<h2 id="install">Installation &amp; Uninstallation</h2>
<p><b>LOOT does not support Windows XP or earlier.</b>
<p><strong>LOOT requires Windows 7 or later.</strong></p>
<p>LOOT can be installed either using its automated installer or manually. To install LOOT manually, extract the downloaded archive to a location of your choice.