mirror of
https://github.com/loot/libloot.git
synced 2026-07-27 14:16:01 -07:00
HTTPSify the World!
In the quest to encrypt all web traffic, let us go ahead and become a bit better netizens by actually pointing people to HTTPS resources when they're available, instead of their HTTP counterparts. The commits were done partially "by hand" (with the help of `git grep`!) and partially using `sed` commands (esp. for the GNU and loot.github.io commits). PR: https://github.com/loot/loot/pull/619
This commit is contained in:
Frederik “Freso” S. Olesen
+1
-1
@@ -43,7 +43,7 @@ First check that an [Inno Setup translation](http://www.jrsoftware.org/files/ist
|
||||
|
||||
### Translating the LOOT application
|
||||
|
||||
1. Download and install the latest version of [Poedit](http://www.poedit.net/).
|
||||
1. Download and install the latest version of [Poedit](https://poedit.net/).
|
||||
2. If you are starting a new translation, select `File->New catalogue from POT file...` and choose the template file at `resources/l10n/template.pot`. In the `Catalog properties` dialog, just click `OK` without changing anything.
|
||||
3. If you are updating a previous translation, open in Poedit the `loot.po` translation file in the relevant subdirectory of `resources/l10n`, then select `Catalogue->Update from POT file...` and choose the template file you downloaded. Click `OK` in the `Update summary` dialog.
|
||||
4. Edit the translation file to add or update translations of the programs' text. Strings that were added since the last translation are displayed in bold and dark blue, and strings you have edited the translations of are marked with a star to the left of their source text in the main list.
|
||||
|
||||
@@ -25,11 +25,11 @@ For example `LOOT v0.7.0-alpha-2-10-gf6d7e80_dev.7z` was built using the revisio
|
||||
|
||||
## Building LOOT
|
||||
|
||||
LOOT's build process uses [CMake](http://cmake.org). Most of LOOT's C++ dependencies are managed by CMake, but the following must be obtained manually:
|
||||
LOOT's build process uses [CMake](https://cmake.org). Most of LOOT's C++ dependencies are managed by CMake, but the following must be obtained manually:
|
||||
|
||||
* [Boost](http://www.boost.org) v1.55+
|
||||
|
||||
Building LOOT's GUI also uses [Node.js](http://nodejs.org/). With it installed, run `npm install` then `node_modules/.bin/bower install` from the repository root to install the additional tools and dependencies required.
|
||||
Building LOOT's GUI also uses [Node.js](https://nodejs.org/). With it installed, run `npm install` then `node_modules/.bin/bower install` from the repository root to install the additional tools and dependencies required.
|
||||
|
||||
The GUI's HTML file is automatically built when building the LOOT GUI binary, but it can also be built by running `node scripts/vulcanize.js` from the repository root.
|
||||
|
||||
@@ -52,4 +52,4 @@ Packaging scripts are provided for creating an installer on Windows and compress
|
||||
|
||||
Run the `scripts/installer.iss` [Inno Setup](http://www.jrsoftware.org/isinfo.php) script to build an installer executable in the `build` folder. If the unofficial Korean and Simplified Chinese Inno Setup translation files are installed alongside the official translation files, then the installer script will also offer those language options. If they are not found, the installer will be built without them.
|
||||
|
||||
The archive packaging script requires [Git](http://git-scm.com/), and on Windows it also requires [7-Zip](http://7-zip.org), while on Linux it requires `tar` and `xz`. It can be run using `node scripts/archive.js`, and creates archives for LOOT, its API and the metadata validator in the `build` folder. The archives are named as described in the Downloads section above.
|
||||
The archive packaging script requires [Git](https://git-scm.com/), and on Windows it also requires [7-Zip](http://7-zip.org), while on Linux it requires `tar` and `xz`. It can be run using `node scripts/archive.js`, and creates archives for LOOT, its API and the metadata validator in the `build` folder. The archives are named as described in the Downloads section above.
|
||||
|
||||
@@ -184,7 +184,7 @@ var {
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
-->
|
||||
|
||||
<h1>LOOT Metadata Syntax</h1>
|
||||
|
||||
@@ -188,7 +188,7 @@ figure > div {
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
-->
|
||||
|
||||
<h1>LOOT</h1>
|
||||
@@ -459,7 +459,7 @@ figure > div {
|
||||
<tr><td>Master File<td>The game's main master file. This is checked for when detecting if the game is installed.
|
||||
<tr><td id="settingsMasterlistURL">Masterlist Repository URL<td>The URL of the repository that LOOT uses to update its local copy of the masterlist. If left empty, masterlist updating will be skipped.
|
||||
<br><br>
|
||||
Masterlist repositories are <a href="http://git-scm.com/">Git</a> repositories that are configured to allow unauthenticated read access and contain a masterlist file named <code>masterlist.yaml</code> in their root directory. The LOOT team maintains a set of official repositories for the games that LOOT supports by default.
|
||||
Masterlist repositories are <a href="https://git-scm.com/">Git</a> repositories that are configured to allow unauthenticated read access and contain a masterlist file named <code>masterlist.yaml</code> in their root directory. The LOOT team maintains a set of official repositories for the games that LOOT supports by default.
|
||||
<tr><td>Masterlist Repository Branch<td>The branch of the masterlist repository that LOOT should get masterlist updates from.
|
||||
<tr><td>Install Path<td>The path to the game's folder, in which the Data folder lies. Either this or a registry key must be supplied.
|
||||
<tr><td>Install Path Registry Key<td>The registry key, in <code>HKEY_LOCAL_MACHINE</code>, that contains the install path of the game. This is used to obtain the install path if LOOT has no previous record of the game's install path, or LOOT's stored install path is invalid. Either this or an install path must be supplied.
|
||||
@@ -470,11 +470,11 @@ figure > div {
|
||||
|
||||
|
||||
<h2 id="contrib">Contributing & Support</h2>
|
||||
<p>LOOT is very much a community project, and contributions from its users are very welcome, whether they be metadata, translations, code or anything else. The best way to contribute is to <a href="https://loot.github.io/docs/contributing/How-To-Contribute">make changes yourself</a> at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our <a href="http://loot.github.io/credits/">credits</a>.
|
||||
<p>LOOT is very much a community project, and contributions from its users are very welcome, whether they be metadata, translations, code or anything else. The best way to contribute is to <a href="https://loot.github.io/docs/contributing/How-To-Contribute">make changes yourself</a> at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our <a href="https://loot.github.io/credits/">credits</a>.
|
||||
|
||||
<p>If you encounter an issue with LOOT, check the <a href="https://loot.github.io/docs/help/LOOT-FAQs">Frequently Asked Questions</a> page in case a solution is available there.
|
||||
|
||||
<p>Otherwise, general discussion and support takes place in LOOT's official forum thread, which is linked to on <a href="http://loot.github.io">LOOT's homepage</a>.
|
||||
<p>Otherwise, general discussion and support takes place in LOOT's official forum thread, which is linked to on <a href="https://loot.github.io">LOOT's homepage</a>.
|
||||
|
||||
<p>If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install, then use the <a href="#copyMetadata">Copy Metadata</a> feature to easily get it in a form that you can then edit into a masterlist on GitHub or post in the official forum threads.
|
||||
|
||||
@@ -482,8 +482,8 @@ figure > div {
|
||||
|
||||
|
||||
<h2 id="credits">Credits</h2>
|
||||
<p>LOOT is developed on <a href="https://github.com/loot/">GitHub</a>, and a full list of GitHub contributors may be found <a href="http://loot.github.io/credits/">here</a>.
|
||||
<p>LOOT's masterlists were largely converted from <a href="http://boss-developers.github.io">BOSS</a>'s masterlists, and so credit is due to the very large number of sources and people who have contributed to them.
|
||||
<p>LOOT is developed on <a href="https://github.com/loot/">GitHub</a>, and a full list of GitHub contributors may be found <a href="https://loot.github.io/credits/">here</a>.
|
||||
<p>LOOT's masterlists were largely converted from <a href="https://boss-developers.github.io">BOSS</a>'s masterlists, and so credit is due to the very large number of sources and people who have contributed to them.
|
||||
<p>In addition, the following are credited with application-related support:
|
||||
<ul>
|
||||
<li>Original icon: jonwd7
|
||||
@@ -515,7 +515,7 @@ figure > div {
|
||||
<a href="https://github.com/loot/yaml-cpp">yaml-cpp</a> libraries, and the <a href="https://bitbucket.org/chromiumembedded/cef">Chromium Embedded Framework</a>. Copyright license information for all these may be found <a href="licenses/Licenses.txt">here</a>.
|
||||
|
||||
<h2 id="license">License</h2>
|
||||
<p>LOOT is distributed under the <a href="http://www.gnu.org/licenses/gpl.html">GNU General Public License v3.0</a>, aside from the documentation, which is distributed under the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License v1.3</a>. The full texts of the licenses are included with LOOT in the accompanying <a href="licenses/GNU%20GPL%20v3.txt">GNU GPL v3.txt</a> and <a href="licenses/GNU%20FDL%20v1.3.txt">GNU FDL v1.3.txt</a> files.
|
||||
<p>LOOT is distributed under the <a href="https://www.gnu.org/licenses/gpl.html">GNU General Public License v3.0</a>, aside from the documentation, which is distributed under the <a href="https://www.gnu.org/licenses/fdl.html">GNU Free Documentation License v1.3</a>. The full texts of the licenses are included with LOOT in the accompanying <a href="licenses/GNU%20GPL%20v3.txt">GNU GPL v3.txt</a> and <a href="licenses/GNU%20FDL%20v1.3.txt">GNU FDL v1.3.txt</a> files.
|
||||
|
||||
<p>While the GPL license allows anyone to make derivative works of LOOT, the LOOT Team encourages those thinking of doing so to first discuss their reasoning for such an endeavour with the Team. It may be that what the derivative work would do differently is already planned for a future version of LOOT or would be happily integrated into LOOT, thus avoiding any extra effort by others.
|
||||
|
||||
|
||||
+7
-7
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
/**
|
||||
@@ -50,13 +50,13 @@
|
||||
*
|
||||
* @section credit_sec Credits
|
||||
* The LOOT API is written by [WrinklyNinja]
|
||||
* (http://github.com/WrinklyNinja) in C/C++ and makes use of the
|
||||
* (https://github.com/WrinklyNinja) in C/C++ and makes use of the
|
||||
* [Boost](http://www.boost.org/),
|
||||
* [libespm](http://github.com/WrinklyNinja/libespm),
|
||||
* [libgit2](http://github.com/libgit2/libgit2),
|
||||
* [libloadorder](http://github.com/WrinklyNinja/libloadorder/),
|
||||
* [Pseudosem](http://github.com/WrinklyNinja/pseudosem) and
|
||||
* [yaml-cpp](http://github.com/WrinklyNinja/yaml-cpp) libraries. Copyright
|
||||
* [libespm](https://github.com/WrinklyNinja/libespm),
|
||||
* [libgit2](https://github.com/libgit2/libgit2),
|
||||
* [libloadorder](https://github.com/WrinklyNinja/libloadorder/),
|
||||
* [Pseudosem](https://github.com/WrinklyNinja/pseudosem) and
|
||||
* [yaml-cpp](https://github.com/WrinklyNinja/yaml-cpp) libraries. Copyright
|
||||
* license information for all these may be found in the
|
||||
* "docs/licenses/Licenses.txt" file.
|
||||
*
|
||||
|
||||
@@ -305,11 +305,11 @@ msgid ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
msgstr ""
|
||||
"Kunne ikke analysere brugerlisten: %1%. Dette skete formentlig fordi en LOOT‐"
|
||||
"opdatering ændrede dets understøttede metadatasyntaks. Dine bruger‐metadata "
|
||||
@@ -318,11 +318,11 @@ msgstr ""
|
||||
"For at gøre dette skal du bruge ‘Åben sted for fejlsøgningslog’ i LOOTs "
|
||||
"hovedmenu til at åbne dets data‐mappe, og herefter åbne din ‘userlist.yaml’‐"
|
||||
"fil i den relevante spilmappe. Du kan nu redigere den metadata filen "
|
||||
"indeholder med reference til [syntaksdokumentationen](http://loot.github.io/"
|
||||
"indeholder med reference til [syntaksdokumentationen](https://loot.github.io/"
|
||||
"docs/%2%.%3%.%4%/LOOT%%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"Du kan også søge hjælp i LOOTs forumtråd, som er linket til på [LOOTs "
|
||||
"hjemmeside](http://loot.github.io/)."
|
||||
"hjemmeside](https://loot.github.io/)."
|
||||
|
||||
#: gui/handler.cpp:708
|
||||
msgid "Merging and evaluating plugin metadata..."
|
||||
|
||||
@@ -312,11 +312,11 @@ msgid ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
msgstr ""
|
||||
"Une erreur s'est produite lors de l'analyse de l'userlist : %1%. Cela est "
|
||||
"probablement arrivé parce qu'une mise à jour de LOOT a modifié sa prise "
|
||||
@@ -326,11 +326,11 @@ msgstr ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
|
||||
#: gui/handler.cpp:725
|
||||
msgid "Merging and evaluating plugin metadata..."
|
||||
|
||||
@@ -310,11 +310,11 @@ msgid ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
msgstr ""
|
||||
"Во время обработки мастерлиста произошла ошибка: %1%. Возможно это произошло "
|
||||
"потому, что в обновлении LOOT изменена поддержка синтаксиса метаданных. "
|
||||
@@ -324,11 +324,11 @@ msgstr ""
|
||||
"главном меню LOOT, для открытия папки с данными, тогда откройте ваш файл "
|
||||
"'userlist.yaml' в соответствующей папке с игрой. Тогда вы сможете "
|
||||
"отредактировать метаданные, содержащиеся в файле в соовтетствии с "
|
||||
"[документацией по синтаксису](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[документацией по синтаксису](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"Можете также поискать в официальной ветке форума по LOOT, ссылку на которую "
|
||||
"можно найти на [сайте LOOT](http://loot.github.io/)."
|
||||
"можно найти на [сайте LOOT](https://loot.github.io/)."
|
||||
|
||||
#: src/gui/handler.cpp:731
|
||||
msgid "Merging and evaluating plugin metadata..."
|
||||
|
||||
@@ -278,11 +278,11 @@ msgid ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
msgstr ""
|
||||
|
||||
#: gui/handler.cpp:725
|
||||
|
||||
@@ -293,20 +293,20 @@ msgid ""
|
||||
"To do so, use the 'Open Debug Log Location' in LOOT's main menu to open its "
|
||||
"data folder, then open your 'userlist.yaml' file in the relevant game "
|
||||
"folder. You can then edit the metadata it contains with reference to the "
|
||||
"[syntax documentation](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"[syntax documentation](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%"
|
||||
"%20Metadata%%20Syntax.html).\n"
|
||||
"\n"
|
||||
"You can also seek support on LOOT's forum thread, which is linked to on "
|
||||
"[LOOT's website](http://loot.github.io/)."
|
||||
"[LOOT's website](https://loot.github.io/)."
|
||||
msgstr ""
|
||||
"解析用户列表时发生错误：%1%。这可能由于升级 LOOT 时改变了元数据的语法支持。你"
|
||||
"的用户数据必须手动更新。\n"
|
||||
"\n"
|
||||
"要完成更新，请使用 LOOT 主菜单中的 '打开本地调试日志' 功能打开数据目录，然后"
|
||||
"在相关目录打开你的 'userlist.yaml' 文件。你可以编辑这个元数据，请参考 [语法文"
|
||||
"档](http://loot.github.io/docs/%2%.%3%.%4%/LOOT%%20Metadata%%20Syntax."
|
||||
"档](https://loot.github.io/docs/%2%.%3%.%4%/LOOT%%20Metadata%%20Syntax."
|
||||
"html)。\n"
|
||||
"你也可以在 LOOT 论坛寻求支持，链接为 [LOOT官方网站](http://loot.github.io/)。"
|
||||
"你也可以在 LOOT 论坛寻求支持，链接为 [LOOT官方网站](https://loot.github.io/)。"
|
||||
|
||||
#: src/gui/handler.cpp:731
|
||||
msgid "Merging and evaluating plugin metadata..."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
Add-Type -AssemblyName System.IO.Compression.FileSystem
|
||||
|
||||
$boostUrl = 'http://downloads.sourceforge.net/project/boost/boost/1.61.0/boost_1_61_0.7z?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fboost%2Ffiles%2Fboost%2F1.61.0%2F&ts=1468862599&use_mirror=ncu'
|
||||
$boostUrl = 'https://downloads.sourceforge.net/project/boost/boost/1.61.0/boost_1_61_0.7z?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fboost%2Ffiles%2Fboost%2F1.61.0%2F&ts=1468862599&use_mirror=ncu'
|
||||
$boostArchive = 'C:\projects\boost_1_61_0.7z'
|
||||
$boostFolder = 'C:\projects\boost_1_61_0'
|
||||
$boostLibraries = @(
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
#define MyAppName "LOOT"
|
||||
#define MyAppVersion "0.9.1"
|
||||
#define MyAppPublisher "LOOT Team"
|
||||
#define MyAppURL "http://loot.github.io"
|
||||
#define MyAppURL "https://loot.github.io"
|
||||
#define MyAppExeName "LOOT.exe"
|
||||
|
||||
#if FileExists(AddBackslash(CompilerPath) + 'Languages\Korean.isl')
|
||||
|
||||
@@ -16,7 +16,7 @@ function isLibraryMissing {
|
||||
if isLibraryMissing; then
|
||||
cd ~
|
||||
|
||||
wget http://downloads.sourceforge.net/project/boost/boost/1.61.0/${BOOST_BASENAME}.tar.bz2
|
||||
wget https://downloads.sourceforge.net/project/boost/boost/1.61.0/${BOOST_BASENAME}.tar.bz2
|
||||
tar xf ${BOOST_BASENAME}.tar.bz2
|
||||
|
||||
cd $BOOST_BASENAME
|
||||
|
||||
+1
-1
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#include "loot/api.h"
|
||||
|
||||
+1
-1
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#include "api/loot_db.h"
|
||||
|
||||
+1
-1
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#ifndef LOOT_API_LOOT_DB
|
||||
|
||||
@@ -19,7 +19,7 @@ Fallout: New Vegas.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT.If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#include "loot_paths.h"
|
||||
|
||||
@@ -19,7 +19,7 @@ GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#ifndef LOOT_BACKEND_APP_LOOT_PATHS
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#include "backend/app/loot_settings.h"
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with LOOT. If not, see
|
||||
<http://www.gnu.org/licenses/>.
|
||||
<https://www.gnu.org/licenses/>.
|
||||
*/
|
||||
|
||||
#ifndef LOOT_BACKEND_APP_LOOT_SETTINGS
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user