Add scripts to generate prebuilt.

2026-07-27 14:07:05 -07:00 · 2024-06-30 19:43:50 +02:00
91 changed files with 41647 additions and 830 deletions
@@ -2,20 +2,15 @@ name: Build Mob
 on:
  push:
-    branches: [master]
+    branches: master
  pull_request:
    types: [opened, synchronize, reopened]
 env:
  VCPKG_BINARY_SOURCES: ${{ vars.AZ_BLOB_VCPKG_URL != '' && format('clear;x-azblob,{0},{1},readwrite', vars.AZ_BLOB_VCPKG_URL, secrets.AZ_BLOB_SAS) || '' }}
 jobs:
  build:
-    runs-on: windows-2025-vs2026
+    runs-on: windows-2022
    steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v4
      - name: Build Mob
        shell: pwsh
-        run: |
+        run: ./bootstrap.ps1 -Verbose
          $env:VCPKG_ROOT = $env:VCPKG_INSTALLATION_ROOT
          ./bootstrap.ps1 -Verbose
@@ -9,7 +9,7 @@ jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v3
      - name: Check format
        uses: ModOrganizer2/check-formatting-action@master
        with:
@@ -1,25 +0,0 @@
 repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v6.0.0
    hooks:
      - id: trailing-whitespace
        exclude: '^(third-party|licenses)/.*$'
      - id: end-of-file-fixer
        exclude: '^(third-party|licenses)/.*$'
      - id: check-merge-conflict
        exclude: '^(third-party|licenses)/.*$'
      - id: check-case-conflict
        exclude: '^(third-party|licenses)/.*$'
  - repo: https://github.com/pre-commit/mirrors-clang-format
    rev: v21.1.8
    hooks:
    - id: clang-format
      'types_or': [c++, c]
      exclude: '^third-party/.*$'
 ci:
  autofix_commit_msg: "[pre-commit.ci] Auto fixes from pre-commit.com hooks."
  autofix_prs: true
  autoupdate_commit_msg: "[pre-commit.ci] Pre-commit autoupdate."
  autoupdate_schedule: quarterly
  submodules: false
@@ -1,11 +1,6 @@
 cmake_minimum_required(VERSION 3.16)
-project(mob LANGUAGES CXX)
+project(mob)
 find_package(clipp CONFIG REQUIRED)
 find_package(nlohmann_json CONFIG REQUIRED)
 find_package(CURL REQUIRED)
 add_subdirectory(src)
 set_property(DIRECTORY ${PROJECT_SOURCE_DIR} PROPERTY VS_STARTUP_PROJECT mob)
@@ -1,28 +0,0 @@
 {
  "version": 6,
  "configurePresets": [
    {
      "name": "vs2026-windows",
      "generator": "Visual Studio 18 2026",
      "architecture": "x64",
      "binaryDir": "${sourceDir}/build/",
      "toolchainFile": "$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake",
      "cacheVariables": {
        "VCPKG_TARGET_TRIPLET": "x64-windows-static-md",
        "CMAKE_CONFIGURATION_TYPES": "Debug;Release;RelWithDebInfo"
      }
    }
  ],
  "buildPresets": [
    {
      "name": "vs2026-windows",
      "configurePreset": "vs2026-windows",
      "nativeToolOptions": [
        "-m",
        "-noLogo",
        "-p:UseMultiToolTask=true",
        "-p:EnforceProcessCountAcrossBuilds=true"
      ]
    }
  ]
 }
@@ -11,17 +11,41 @@ if (!$root) {
    $root = "."
 }
-$logLevel = if ($Verbose) { "STATUS" } else { "ERROR" }
+$output = if ($Verbose) { "Out-Default" } else { "Out-Null" }
-cmake --preset vs2026-windows --log-level=$logLevel
+cmake -B $root/build $root | & $output
-if ($Verbose) {
+$installationPath = & $root\third-party\bin\vswhere.exe -products * -nologo -prerelease -latest -property installationPath
-    cmake --build --preset vs2026-windows --config $Config --verbose
+if (! $?) {
    Write-Error "vswhere returned $LastExitCode"
    exit $LastExitCode
 }
-else {
+
-    cmake --build --preset vs2026-windows --config $Config
+if (! $installationPath) {
    Write-Error "Empty installation path"
    exit 1
 }
 $opts = ""
 $opts += " $root\build\mob.sln"
 $opts += " -m"
 $opts += " -p:Configuration=${Config}"
 $opts += " -noLogo"
 $opts += " -p:UseMultiToolTask=true"
 $opts += " -p:EnforceProcessCountAcrossBuilds=true"
 if (!$Verbose) {
    $opts += " -clp:ErrorsOnly;Verbosity=minimal"
 }
 $vsDevCmd = "$installationPath\Common7\Tools\VsDevCmd.bat"
 if (!(Test-Path "$vsDevCmd")) {
    Write-Error "VdDevCmd.bat not found at $vsDevCmd"
    exit 1
 }
 & "${env:COMSPEC}" /c "`"$vsDevCmd`" -no_logo -arch=amd64 -host_arch=amd64 && msbuild $opts"
 if (! $?) {
    Write-Error "Build failed"
    exit $LastExitCode
@@ -1 +0,0 @@
 set(VCPKG_POLICY_EMPTY_PACKAGE enabled)
@@ -1,8 +0,0 @@
 {
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "zlib",
  "version-string": "zlib-ng overlay",
  "dependencies": [
    "zlib-ng"
  ]
 }
@@ -1,6 +0,0 @@
 set(VCPKG_TARGET_ARCHITECTURE x64)
 set(VCPKG_CRT_LINKAGE dynamic)
 set(VCPKG_LIBRARY_LINKAGE static)
 set(ZLIB_COMPAT ON)
 set(nlohmann-json_IMPLICIT_CONVERSIONS OFF)
@@ -1,28 +1,27 @@
-  7-Zip source code
+  7-Zip
-  ~~~~~~~~~~~~~~~~~
+  ~~~~~
  License for use and distribution
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-  7-Zip Copyright (C) 1999-2024 Igor Pavlov.
+  7-Zip Copyright (C) 1999-2023 Igor Pavlov.
  The licenses for files are:
-    - CPP/7zip/Compress/Rar* files: the "GNU LGPL" with "unRAR license restriction"
+    1) 7z.dll:
-    - CPP/7zip/Compress/LzfseDecoder.cpp: the "BSD 3-clause License"
+         - The "GNU LGPL" as main license for most of the code
-    - C/ZstdDec.c: the "BSD 3-clause License"
+         - The "GNU LGPL" with "unRAR license restriction" for some code
-    - C/Xxh64.c: the "BSD 2-clause License"
+         - The "BSD 3-clause License" for some code
-    - Some files are "public domain" files, if "public domain" status is stated in source file.
+    2) All other files: the "GNU LGPL".
    - the "GNU LGPL" for all other files. If there is no license information in
       some source file, that file is under the "GNU LGPL".
-  The "GNU LGPL" with "unRAR license restriction" means that you must follow both
+  Redistributions in binary form must reproduce related license information from this file.
-  "GNU LGPL" rules and "unRAR license restriction" rules.
+
  Note:
    You can use 7-Zip on any computer, including a computer in a commercial
    organization. You don't need to register or pay for 7-Zip.
-
+  GNU LGPL information
-
+  --------------------
 GNU LGPL information
 --------------------
    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
@@ -34,118 +33,58 @@ GNU LGPL information
    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
+    You can receive a copy of the GNU Lesser General Public License from
    License along with this library; if not,
    you can get a copy of the GNU Lesser General Public License from
    http://www.gnu.org/
-BSD 3-clause License in 7-Zip code
+  BSD 3-clause License
----------------------------------
+  --------------------
-  The "BSD 3-clause License" is used for the following code in 7z.dll
+    The "BSD 3-clause License" is used for the code in 7z.dll that implements LZFSE data decompression.
-    1) LZFSE data decompression.
+    That code was derived from the code in the "LZFSE compression library" developed by Apple Inc,
-         CPP/7zip/Compress/LzfseDecoder.cpp.
+    that also uses the "BSD 3-clause License":
       That code was derived from the code in the "LZFSE compression library" developed by Apple Inc,
       that also uses the "BSD 3-clause License".
    2) ZSTD data decompression.
         C/ZstdDec.c
       that code was developed using original zstd decoder code as reference code.
       The original zstd decoder code was developed by Facebook Inc,
       that also uses the "BSD 3-clause License".
-  Copyright (c) 2015-2016, Apple Inc. All rights reserved.
+    ----
-  Copyright (c) Facebook, Inc. All rights reserved.
+    Copyright (c) 2015-2016, Apple Inc. All rights reserved.
  Copyright (c) 2023-2024 Igor Pavlov.
-Text of the "BSD 3-clause License"
+    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
 ----------------------------------
-Redistribution and use in source and binary forms, with or without modification,
+    1.  Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
 are permitted provided that the following conditions are met:
-1. Redistributions of source code must retain the above copyright notice, this
+    2.  Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
-   list of conditions and the following disclaimer.
+        in the documentation and/or other materials provided with the distribution.
-2. Redistributions in binary form must reproduce the above copyright notice,
+    3.  Neither the name of the copyright holder(s) nor the names of any contributors may be used to endorse or promote products derived
-   this list of conditions and the following disclaimer in the documentation
+        from this software without specific prior written permission.
   and/or other materials provided with the distribution.
-3. Neither the name of the copyright holder nor the names of its contributors may
+    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-   be used to endorse or promote products derived from this software without
+    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-   specific prior written permission.
+    COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-
+    (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+    ----
 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
 ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
 ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ---
-BSD 2-clause License in 7-Zip code
+  unRAR license restriction
----------------------------------
+  -------------------------
-  The "BSD 2-clause License" is used for the XXH64 code in 7-Zip.
+    The decompression engine for RAR archives was developed using source
-    C/Xxh64.c
+    code of unRAR program.
    All copyrights to original unRAR code are owned by Alexander Roshal.
-  XXH64 code in 7-Zip was derived from the original XXH64 code developed by Yann Collet.
+    The license for original unRAR code has the following restriction:
-  Copyright (c) 2012-2021 Yann Collet.
+      The unRAR sources cannot be used to re-create the RAR compression algorithm,
-  Copyright (c) 2023-2024 Igor Pavlov.
+      which is proprietary. Distribution of modified unRAR sources in separate form
-
+      or as a part of other software is permitted, provided that it is clearly
-Text of the "BSD 2-clause License"
+      stated in the documentation and source comments that the code may
----------------------------------
+      not be used to develop a RAR (WinRAR) compatible archiver.
 Redistribution and use in source and binary forms, with or without modification,
 are permitted provided that the following conditions are met:
 1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
 ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
 ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ---
-
+  --
-
+  Igor Pavlov
 unRAR license restriction
 -------------------------
 The decompression engine for RAR archives was developed using source
 code of unRAR program.
 All copyrights to original unRAR code are owned by Alexander Roshal.
 The license for original unRAR code has the following restriction:
  The unRAR sources cannot be used to re-create the RAR compression algorithm,
  which is proprietary. Distribution of modified unRAR sources in separate form
  or as a part of other software is permitted, provided that it is clearly
  stated in the documentation and source comments that the code may
  not be used to develop a RAR (WinRAR) compatible archiver.
 --
@@ -1,4 +1,4 @@
-Copyright (c) 2012 - present, Victor Zverovich and {fmt} contributors
+Copyright (c) 2012 - present, Victor Zverovich
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
@@ -2,12 +2,12 @@ A. HISTORY OF THE SOFTWARE
 ==========================
 Python was created in the early 1990s by Guido van Rossum at Stichting
-Mathematisch Centrum (CWI, see https://www.cwi.nl) in the Netherlands
+Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
 as a successor of a language called ABC.  Guido remains Python's
 principal author, although it includes many contributions from others.
 In 1995, Guido continued his work on Python at the Corporation for
-National Research Initiatives (CNRI, see https://www.cnri.reston.va.us)
+National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
 in Reston, Virginia where he released several versions of the
 software.
@@ -19,7 +19,7 @@ https://www.python.org/psf/) was formed, a non-profit organization
 created specifically to own Python-related Intellectual Property.
 Zope Corporation was a sponsoring member of the PSF.
-All Python releases are Open Source (see https://opensource.org for
+All Python releases are Open Source (see http://www.opensource.org for
 the Open Source Definition).  Historically, most, but not all, Python
 releases have also been GPL-compatible; the table below summarizes
 the various releases.
@@ -84,7 +84,7 @@ analyze, test, perform and/or display publicly, prepare derivative works,
 distribute, and otherwise use Python alone or in any derivative version,
 provided, however, that PSF's License Agreement and PSF's notice of copyright,
 i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023 Python Software Foundation;
+2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 Python Software Foundation;
 All Rights Reserved" are retained in Python alone or in any derivative version
 prepared by Licensee.
@@ -191,9 +191,9 @@ version prepared by Licensee.  Alternately, in lieu of CNRI's License
 Agreement, Licensee may substitute the following text (omitting the
 quotes): "Python 1.6.1 is made available subject to the terms and
 conditions in CNRI's License Agreement.  This Agreement together with
-Python 1.6.1 may be located on the internet using the following
+Python 1.6.1 may be located on the Internet using the following
 unique, persistent identifier (known as a handle): 1895.22/1013.  This
-Agreement may also be obtained from a proxy server on the internet
+Agreement may also be obtained from a proxy server on the Internet
 using the following URL: http://hdl.handle.net/1895.22/1013".
 3. In the event Licensee prepares a derivative work that is based on
@@ -1,22 +1,49 @@
-Copyright 2024 Phil Thompson <phil@riverbankcomputing.com>
+RIVERBANK COMPUTING LIMITED LICENSE AGREEMENT FOR SIP
-Redistribution and use in source and binary forms, with or without
+1. This LICENSE AGREEMENT ("the SIP License") is between Riverbank Computing
-modification, are permitted provided that the following conditions are met:
+Limited ("Riverbank"), and the Individual or Organization ("Licensee")
 accessing and otherwise using SIP software in source or binary form and its
 associated documentation.  SIP comprises a software tool for generating Python
 bindings for software C and C++ libraries, and a Python extension module used
 at runtime by those generated bindings.  This License Agreement may also be
 applied to other software packages written by Riverbank.
-1. Redistributions of source code must retain the above copyright notice, this
+2. Subject to the terms and conditions of this License Agreement, Riverbank
-list of conditions and the following disclaimer.
+hereby grants Licensee a nonexclusive, royalty-free, world-wide license to
 reproduce, analyze, test, perform and/or display publicly, prepare derivative
 works, distribute, and otherwise use SIP alone or in any derivative version,
 provided, however, that Riverbank's License Agreement and Riverbank's notice of
 copyright, e.g., "Copyright (c) 2015 Riverbank Computing Limited; All Rights
 Reserved" are retained in SIP alone or in any derivative version prepared by
 Licensee.
-2. Redistributions in binary form must reproduce the above copyright notice,
+3. In the event Licensee prepares a derivative work that is based on or
-this list of conditions and the following disclaimer in the documentation
+incorporates SIP or any part thereof, and wants to make the derivative work
-and/or other materials provided with the distribution.
+available to others as provided herein, then Licensee hereby agrees to include
 in any such work a brief summary of the changes made to SIP.
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND
+4. Licensee may not use SIP to generate Python bindings for any C or C++
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+library for which bindings are already provided by Riverbank.
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+5. Riverbank is making SIP available to Licensee on an "AS IS" basis.
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+RIVERBANK MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED.  BY WAY
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+OF EXAMPLE, BUT NOT LIMITATION, RIVERBANK MAKES NO AND DISCLAIMS ANY
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+PURPOSE OR THAT THE USE OF SIP WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+6. RIVERBANK SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF SIP FOR ANY
 INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING,
 DISTRIBUTING, OR OTHERWISE USING SIP, OR ANY DERIVATIVE THEREOF, EVEN IF
 ADVISED OF THE POSSIBILITY THEREOF.
 7. This License Agreement will automatically terminate upon a material breach
 of its terms and conditions.
 8. Nothing in this License Agreement shall be deemed to create any relationship
 of agency, partnership, or joint venture between Riverbank and Licensee.  This
 License Agreement does not grant permission to use Riverbank trademarks or
 trade name in a trademark sense to endorse or promote products or services of
 Licensee, or any third party.
 9. By copying, installing or otherwise using SIP, Licensee agrees to be bound
 by the terms and conditions of this License Agreement.
@@ -22,5 +22,5 @@ THE SOFTWARE.
 -- NOTE: Third party dependency used by this software --
 This software depends on the fmt lib (MIT License),
-and users must comply to its license: https://raw.githubusercontent.com/fmtlib/fmt/master/LICENSE
+and users must comply to its license: https://github.com/fmtlib/fmt/blob/master/LICENSE.rst
@@ -1,6 +1,4 @@
-Copyright notice:
+ (C) 1995-2017 Jean-loup Gailly and Mark Adler
 (C) 1995-2022 Jean-loup Gailly and Mark Adler
  This software is provided 'as-is', without any express or implied
  warranty.  In no event will the authors be held liable for any damages
@@ -47,7 +47,6 @@ git_shallow = false
 [usvfs:task]
 git_shallow = false
 configuration = Release
 [installer:task]
 enabled = false
@@ -85,14 +84,39 @@ force     = false
 configure = true
 pull      = true
 [prebuilt]
 boost   = true
 lz4     = true
 openssl = true
 pyqt    = true
 python  = true
 [versions]
 vs             = 17
 vs_year        = 2022
 vs_toolset     = 14.3
-sdk            = 10.0.26100.0
+sdk            = 10.0.22621.0
-pyqt           = 6.7.1
+sevenz         = 24.05
-qt             = 6.7.3
+boost          = 1.85.0
-qt_vs          = 2022
+boost_vs       = 14.3
 fmt            = 10.2.1
 gtest          = main
 libloot        = 0.22.4
 lz4            = v1.9.4
 nmm            = 0.71.2
 openssl        = 3.3.0
 pyqt           = 6.7.0
 pyqt_builder   = 1.16.2
 pyqt_sip       = 13.7.0
 python         = v3.12.3
 pybind11       = v2.12.0
 bzip2          = 1.0.8
 sip            = 6.8.3
 spdlog         = v1.14.1
 qt             = 6.7.0
 qt_vs          = 2019
 zlib           = v1.3.1
 libbsarch      = 0.0.9
 usvfs          = master
 explorerpp     = 1.4.0
 ss_paper_lad_6788      = 7.2
@@ -105,10 +129,16 @@ ss_starfield_trosski   = V1.11
 ss_fallout3_trosski    = v1.11
 ss_fallout4_trosski    = v1.11
 [build-types]
 libbsarch = release
 pyqt = release
 python = release
 [paths]
 third_party          =
 prefix               =
 cache                =
 patches              =
 licenses             =
 build                =
 install              =
@@ -117,12 +147,13 @@ install_installer    =
 install_libs         =
 install_pdbs         =
 install_dlls         =
 install_loot         =
 install_plugins      =
 install_stylesheets  =
 install_licenses     =
 install_pythoncore   =
 install_translations =
 vs                   =
 vcpkg                =
 qt_install           =
 qt_bin               =
 qt_translations      =
@@ -0,0 +1,36 @@
 --- builder.py	(date 1575938575861)
 +++ builder.py	(date 1575938575861)
@@ -402,17 +402,29 @@
                     'QMAKE_LFLAGS += -Wl,--version-script={}.exp'.format(
                             buildable.target))
 -        pro_lines.append(
 +        if project.py_platform == 'win32':
 +            for include_dir in project.py_include_dir.split(';'):
 +                pro_lines.append(
 +                        'INCLUDEPATH += {}'.format(
 +                                self.qmake_quote(include_dir)))
 +        else:
 +            pro_lines.append(
                 'INCLUDEPATH += {}'.format(
 -                        self.qmake_quote(project.py_include_dir)))
 +                    self.qmake_quote(project.py_include_dir)))
 +        if project.py_pylib_shlib != "":
 +            pro_lines.append(
 +                    'DEFINES += {}'.format(
 +                        self.qmake_quote("PYTHON_LIB=\"{}\"".format(
 +                                project.py_pylib_shlib))))
 +
         # Python.h on Windows seems to embed the need for pythonXY.lib, so tell
         # it where it is.
         # TODO: is this still necessary for Python v3.8?
         if not buildable.static:
             pro_lines.extend(['win32 {',
 -                    '    LIBS += -L{}'.format(
 -                            self.qmake_quote(project.py_pylib_dir)),
 +                    '    LIBS += -L{}{}'.format(
 +                            self.qmake_quote(project.py_pylib_dir), '' if project.py_pylib_lib == '' else ' -l' + project.py_pylib_lib),
                     '}'])
         # Add any installables from the buildable
@@ -0,0 +1,10 @@
 --- PCbuild/openssl.props	(revision 5c02a39a0b31a330e06b4d6f44835afb205dc7cc)
 +++ PCbuild/openssl.props	(date 1575994670797)
@@ -13,6 +13,7 @@
     <_DLLSuffix>-3</_DLLSuffix>
     <_DLLSuffix Condition="$(Platform) == 'ARM'">$(_DLLSuffix)-arm</_DLLSuffix>
     <_DLLSuffix Condition="$(Platform) == 'ARM64'">$(_DLLSuffix)-arm64</_DLLSuffix>
 +    <_DLLSuffix Condition="$(Platform) == 'x64'">$(_DLLSuffix)-x64</_DLLSuffix>
     <OpenSSLDLLSuffix Condition="$(OpenSSLDLLSuffix) == ''">$(_DLLSuffix)</OpenSSLDLLSuffix>
   </PropertyGroup>
   <ItemGroup>
@@ -1,85 +1,63 @@
 # `mob` - ModOrganizer Build Tool
 This README explains how to use `mob` and build ModOrganizer2 with it.
 If you want to contribute to a single plugin of MO2 or even write your own plugins,
 check the [ModOrganizer2 Wiki](https://github.com/ModOrganizer2/modorganizer/wiki).
 ## Table of contents
 - [Quick start](#quick-start)
- [Extended start](#extended-start)
+- [Slow start](#slow-start)
 - [Changing options](#changing-options)
-  - [INI files](#override-options-using-ini-files)
+  * [INI files](#ini-files)
-  - [Command line](#override-options-using-command-line)
+  * [Command line](#command-line)
-  - [INI format](#ini-format)
+  * [INI format](#ini-format)
 - [Options](#options)
-  - [`[global]`](#global)
+  * [`[global]`](#global)
-  - [`[task]`](#task)
+  * [`[task]`](#task)
-  - [`[tools]`](#tools)
+  * [`[tools]`](#tools)
-  - [`[versions]`](#versions)
+  * [`[prebuilt]`](#prebuilt)
-  - [`[paths]`](#paths)
+  * [`[versions]`](#versions)
- [Command line](#command-line)
+  * [`[paths]`](#paths)
-  - [Global options](#global-options)
+- [Command line](#command-line-1)
-  - [`build`](#build)
+  * [Global options](#global-options)
-  - [`list`](#list)
+  * [`build`](#build)
-  - [`options`](#options)
+  * [`list`](#list)
-  - [`release`](#release)
+  * [`options`](#options)
-  - [`git`](#git)
+  * [`release`](#release)
-  - [`cmake-config`](#cmake-config)
+  * [`git`](#git)
-  - [`inis`](#inis)
+  * [`cmake`](#cmake)
  * [`inis`](#inis)
 ## Quick start
 ```powershell
-git clone https://github.com/ModOrganizer2/mob
+> git clone https://github.com/ModOrganizer2/mob
-cd mob
+> cd mob
-$env:VCPKG_ROOT = "C:\path\to\vcpkg"
+> bootstrap
-./bootstrap
+> mob -d c:\somewhere build
 mob -d c:\somewhere build
 ```
 ## Extended start
-### Qt Installation
+### Qt - CLI based install using [aqt](https://github.com/miurahr/aqtinstall)
-Check [`mob.ini`](https://github.com/ModOrganizer2/mob/blob/master/mob.ini#L94) to find
+[aqt](https://github.com/miurahr/aqtinstall) is a CLI installer for Qt, it makes installing Qt extremely quick and painless, and doesn't require a login
 out which version of Qt you need.
-#### CLI based install using [aqt](https://github.com/miurahr/aqtinstall)
+#### Installing aqt via package manager
 - Start an administrative terminal
 - Install aqt using one of the two popular packaage managers
  - `winget install --id=miurahr.aqtinstall  -e`
  - `choco install aqt`
-[aqt](https://github.com/miurahr/aqtinstall) is a CLI installer for Qt, it makes
+#### Installing aqt via python/pip
 installing Qt extremely quick and painless, and doesn't require a login.
 Check the [documentation](https://aqtinstall.readthedocs.io/en/latest/installation.html)
 to install **aqt** itself.
-> [!IMPORTANT]
+- Install [Python 3.9](https://www.python.org/downloads/release/python-390/)
-> As of version 3.3.0, **aqt** is unable to install Qt version 6.7.3 on the
+- Install [aqt](https://github.com/miurahr/aqtinstall) using `pip`
 > `win64_msvc2022_64` target architecture due to a non-standard download URL (see:
 > miurahr/aqtinstall#919). The [Holt59/aqtinstall fork](https://github.com/Holt59/aqtinstall)
 > provides a workaround for this issue and can be installed using the following command
 > (requires Python 3.9 or above):
 > ```powershell
 > pip install git+https://github.com/Holt59/aqtinstall.git#egg=aqtinstall
 > ```
 > If you already installed **aqt** before, you first need to uninstall it before
 > installing the fork:
 > ```powershell
 > pip uninstall aqtinstall
 > ```
 When using **aqt**, you can choose which modules to install but we recommend installing
 all of them in case of changes.
 #### Using aqt
 - Open a terminal with administrative rights, and run
 ```powershell
-# you can also use -m all to install all modules
+aqt install-qt --outputdir "C:\Qt" windows desktop 6.7.0 win64_msvc2019_64 -m qtwebengine qtimageformats qtpositioning qtserialport qtwebchannel qtwebsockets
 aqt install-qt --outputdir "C:\Qt" windows desktop ${QT_VERSION} win64_msvc2022_64 `
  -m qtwebengine qtimageformats qtpositioning qtserialport qtwebchannel qtwebsockets
 ```
-#### Manual installation
+### Qt - Manual installation
-
+- Install Qt 6.7.0 ([Installer](https://download.qt.io/official_releases/online_installers/qt-unified-windows-x64-online.exe)) and select these components:
- Install Qt  ([Installer](https://download.qt.io/official_releases/online_installers/qt-unified-windows-x64-online.exe)) and select these components:
+  - MSVC 2019 64-bit
  - MSVC 2022 64-bit
  - Additional Libraries:
    - Qt WebEngine (display nexus pages)
    - Qt Image Formats (display images in image tab and preview)
@@ -92,15 +70,12 @@ aqt install-qt --outputdir "C:\Qt" windows desktop ${QT_VERSION} win64_msvc2022_
    - Qt Debug Files
 ### Visual Studio
 - Install Visual Studio 2022 ([Installer](https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&channel=Release&version=VS2022&source=VSLandingPage&cid=2030&passive=false))
  - Desktop development with C++
  - Desktop .NET desktop development (needed by OMOD and FOMOD installers)
  - Individual Components:
    - .Net Framework 4.8 SDK
-    - .Net Framework 4.7.2 targeting pack  (OMOD targets 4.8 but VS still requires
+    - .Net Framework 4.7.2 targeting pack  (OMOD targets 4.8 but VS still requires the package for other .Net components)
      the package for other .Net components)
    - Windows Universal C Runtime
    - C++ ATL for latest v143 build Tools (x86 & x64)
    - C++ /CLI support for v143 build Tools (Latest)  (for OMOD and FOMOD installers)
@@ -109,80 +84,45 @@ aqt install-qt --outputdir "C:\Qt" windows desktop ${QT_VERSION} win64_msvc2022_
    - Git for Windows (Skip if you have this already installed outside of the VS installer)
    - CMake tools for Windows (Skip if you have this already installed outside of the VS installer)
 ### vcpkg
 `mob` now uses **vcpkg** to manage its third-party dependencies (like libcurl).
 1. **Install vcpkg**: If you don't have it, follow the [official instructions](https://learn.microsoft.com/en-us/vcpkg/get_started/get-started).
 2. **Set Environment Variable**: `mob` requires the `VCPKG_ROOT` environment variable to locate the toolchain.
   ```powershell
    $env:VCPKG_ROOT = "C:\path\to\vcpkg"
    $env:PATH = "$env:VCPKG_ROOT;$env:PATH"
   ```
 3. **Static Triplet**: `mob` builds with the `x64-windows-static-md` triplet by default to ensure a standalone executable. The `bootstrap.ps1` script handles this automatically if `VCPKG_ROOT` is set.
 ## Setting up MOB
-
+- Open a shell. If you've installed Git or CMake through the VS installer, they won't be on your PATH, so you must use x64 Native Tools Command Prompt for VS 2022.- Pick a folder to develop MO2 in, for these steps it'll be `C:\dev`
 - Execute these commands
 ```powershell
 mkdir C:\dev
 cd C:\dev
 # clone this repository
 git clone https://github.com/ModOrganizer2/mob
 # set vcpkg path, or use `vcpkg integrate install` instead
 $env:VCPKG_ROOT = "C:\path\to\your\vcpkg"
 # build mob itself - this will create mob.exe in the current directory
 ./bootstrap.ps1
 # build MO2 itself - this will take a LONG time
 mob -d C:\dev\modorganizer build
 ```
 - Once `mob` is finished, everything will be in `C:\dev\modorganizer`. Mod Organizer can be run from `install\bin\ModOrganizer.exe`. The Visual Studio solution for Mod Organizer itself is `build\modorganizer_super\modorganizer\vsbuild\organizer.sln`.
 ### Prebuilts
 Some third-parties are not normally built from source, but this can be changed in the options by setting the various tasks in `[prebuilt]` to `false`. If OpenSSL is built from source, perl is required ([Strawberry Perl 5.30.2.1 installer](http://strawberryperl.com/download/5.30.2.1/strawberry-perl-5.30.2.1-64bit.msi)).
 Once `mob` is finished, everything will be in `C:\dev\modorganizer`.
 Mod Organizer can be run from `install\bin\ModOrganizer.exe`.
 The Visual Studio solution for Mod Organizer itself is `build\modorganizer_super\modorganizer\vsbuild\organizer.sln`.
 ## Changing options
 `mob` has two ways of setting options: from INI files, the `MOBINI` environment variable, or from the command line.
-`mob` has two ways of setting options: from INI files, the `MOBINI` environment
+### INI files
-variable, or from the command line.
+`mob` builds a list of available INI files in order of priority. Higher numbers override lower numbers:
 ### Override options using INI files
 `mob` builds a list of available INI files in order of priority. Higher numbers
 override lower numbers:
 1) The master INI `mob.ini` in the directory where `mob.exe` lives (required).
 2) Any files set in `MOBINI` (separated by semicolons).
 3) Another `mob.ini` in the current directory.
 4) Files given with `--ini`.
-Use `mob inis` to see the list of INI files in order. If `--no-default-inis` is given,
+Use `mob inis` to see the list of INI files in order. If `--no-default-inis` is given, `mob` will skip 1) and 2). The first INI it finds after that is considered the master.
 `mob` will skip 1) and 2). The first INI it finds after that is considered the master.
-### Override options using command line
+### Command line
-
+Any option can be overridden from the command like with `-s task:section/key=value`, where `task:` is optional. Some options have shortcuts, such as `--dry` for `-s global/dry=true` and `-l5` for `-s global:output_log_level=5`. See `mob options` for the list of options.
 Any option can be overridden from the command like with `-s task:section/key=value`,
 where `task:` is optional. Some options have shortcuts, such as `--dry`
 for `-s global/dry=true` and `-l5` for `-s global:output_log_level=5`.
 See `mob options` for the list of options.
 ### INI format
 Inside the INI file are `[sections]` and `key = value` pairs. The `[task]` section is special because it can be changed for specific tasks instead of globally. Any value under a `[task_name:task]` section will only apply to a task named `task_name`. The list of available tasks can be seen with `mob list`. See [Task names](#task-names).
 Inside the INI file are `[sections]` and `key = value` pairs. The `[task]` section is
 special because it can be changed for specific tasks instead of globally.
 Any value under a `[task_name:task]` section will only apply to a task
 named `task_name`. The list of available tasks can be seen with `mob list`.
 See [Task names](#task-names).
 ## Options
 ### `[global]`
 | Option             | Type | Description |
 | ---                | ---  | ---         |
 | `dry`              | bool | Whether filesystem operations are simulated. Note that many operations will fail and that the build process will most probably not complete. This is mostly useful to get a dump of the options. |
@@ -193,13 +133,12 @@ See [Task names](#task-names).
 | `clean_task`       | bool | For `build`, whether tasks are cleaned. |
 | `fetch_task`       | bool | For `build`, whether tasks are fetched (download, git, etc.) |
 | `build_task`       | bool | For `build`, whether tasks are built (msbuild, jobm etc.) |
-| `output_log_level` | [0-6]| The log level for stdout: 0=silent, 1=errors, 2=warnings, 3=info (default), 4=debug, 5=trace, 6=dump. Note that 6 will dump _a lot_ of stuff, such as debug information from curl during downloads. |
+| `output_log_level` | [0-6]| The log level for stdout: 0=silent, 1=errors, 2=warnings, 3=info (default), 4=debug, 5=trace, 6=dump. Note that 6 will dump _a lot_ of stuff, such as debug information from curl during downloads.
 | `file_log_level`   | [0-6]| The log level for the log file. |
 | `log_file`         | path | The path to a log file. |
 | `ignore_uncommitted` | bool | When `--redownload` or `--reextract` is given, directories controlled by git will be deleted even if they contain uncommitted changes.|
 ### `[task]`
 Options for individual tasks. Can be `[task_name:task]`, where `task_name` is the name of a task (see `mob list`) , `super` for all MO tasks or a glob like `installer_*`.
 | Option          | Type   | Description |
@@ -208,21 +147,20 @@ Options for individual tasks. Can be `[task_name:task]`, where `task_name` is th
 | `configuration` | enum   | Which configuration to build, should be one of Debug, Release or RelWithDebInfo with RelWithDebInfo being the default.|
 #### Common git options
 Unless otherwise stated, applies to any task that is a git repo.
 | Option      | Type   | Description |
 | ---         | ---    | ---         |
 | `mo_org`    | string | The organisation name when pulling from Github. Only applies to ModOrganizer projects, plus NCC and usvfs. |
 | `mo_branch` | string | The branch name when pulling from Github. Only applies to ModOrganizer projects, plus NCC and usvfs. |
-| `mo_master` | string | The fallback branch name when pulling from Github. Only applies to ModOrganizer projects, plus NCC and usvfs. This branch is used when `mo_branch` does not exists. If this value is empty, the fallback mechanism is disabled (default behavior). |
+| `mo_master` | string | The fallback branch name when pulling from Github. Only applies to ModOrganizer projects, plus NCC and usvfs.
 This branch is used when `mo_branch` does not exists. If this value is empty, the fallback mechanism is disabled (default behavior). |
 | `no_pull`   | bool   | If a repo is already cloned, a `git pull` will be done on it every time `mob build` is run. Set to `false` to never pull and build with whatever is in there. |
 | `ignore_ts` | bool   | Marks all the `.ts` files in a repo with `--assume-unchanged`. Note that `mob git ignore-ts off` can be used to revert it. |
 | `git_url_prefix` | string | When cloning a repo, the URL will be `$(git_url_prefix)mo_org/repo.git`. |
 | `git_shallow` | bool | When true, clones with `--depth 1` to avoid having to fetch all the history. Defaults to true for third-parties. |
 #### Git credentials
 These are used to set `user.name` and `user.email`. Applies to any task that is a git repo.
 | Option         | Type   | Description |
@@ -231,9 +169,7 @@ These are used to set `user.name` and `user.email`. Applies to any task that is
 | `git_email`    | string | Email |
 #### Origin and upstream remotes
 When `git` clones, it automatically creates a remote named `origin` for the URL that was cloned. When `set_origin_remote` is `true`, this will:
 1) Rename `origin` to `upstream`, and
 2) Create a new `origin` with the given parameters.
@@ -247,7 +183,7 @@ When `git` clones, it automatically creates a remote named `origin` for the URL
 For example, this will create an `origin` remote for all ModOrganizer2 projects and mark all `.ts` files as `--assume-unchanged`.
-```ini
+```
 [super:task]
 ignore_ts                  = true
 git_username               = isanae
@@ -260,22 +196,21 @@ remote_push_default_origin = true
 ```
 ### `[tools]`
 The various tools in this section are used verbatim when creating processes and so will be looked in the `PATH` environment variable. `vcvars` is best left empty, it will be found using the `vswhere.exe` that's bundled as a third-party.
-### `[versions]`
+### `[prebuilt]`
 Some tasks can use prebuilt binaries instead of building from source.
 ### `[versions]`
 The versions for all the tasks.
 ### `[paths]`
 The only path that's required is `prefix`, which is where `mob` will put everything. Within this directory will be `build/`, `downloads/` and `install/`. Everything else is derived from it.
-If `mob` is unable to find the Qt installation directory, it can be specified in `qt_install`. This directory should contain `bin/`, `include/`, etc.
+If `mob` is unable to find the Qt installation directory, it can be specified in `qt_install`. This directory should contain `bin/`, `include/`, etc. It's typically something like `C:\Qt\6.5.1\msvc2019_64\`. The other path `qt_bin` will be derived from it, it's just `$qt_install/bin/`.
-It's typically something like `C:\Qt\6.7.3\msvc2022_64\`. The other path `qt_bin` will be derived from it, it's just `$qt_install/bin/`.
+
 ## Command line
 Do `mob --help` for global options and the list of available commands. Do `mob <command> --help` for more help about a command.
 To use global options with command options, ensure command options are together, with no global options in the middle.
@@ -284,15 +219,15 @@ To use global options with command options, ensure command options are together,
 | Option              | Description |
 | ---                 | --- |
-| `--ini`             | Adds an INI file, see [INI files](#override-options-using-ini-files). |
+| `--ini`             | Adds an INI file, see [INI files](#ini-files). |
 | `--dry`             | Simulates filesystem operations. Note that many operations will fail and that the build process will stop with errors. This is mostly useful to get a dump of the options. |
-| `-log-level`        | The log level for stdout: 0=silent, 1=errors, 2=warnings, 3=info (default), 4=debug, 5=trace, 6=dump. Note that 6 will dump _a lot_ of stuff, such as debug information from curl during downloads. |
+| `-log-level`        | The log level for stdout: 0=silent, 1=errors, 2=warnings, 3=info (default), 4=debug, 5=trace, 6=dump. Note that 6 will dump _a lot_ of stuff, such as debug information from curl during downloads.
-| `--destination`     | The build directory where `mob` will put everything. |
+| `--destination`     | The build directory where `mob` will put everything.
-| `--set`             | Sets an option: `-s task:section/key=value`. |
+| `--set`             | Sets an option: `-s task:section/key=value`.
 | `--no-default-inis` | Does not auto detect INI files, only uses `--ini`. |
 ### `build`
 ### `build`
 Builds tasks. The order in which tasks have to be built is handled by `mob`, but dependencies will not be built automatically when specifying tasks manually. That is, `mob build` will build `python` before `pyqt`, but `mob build pyqt` will not build `python`. Many tasks will be able to run in parallel, but not all, either because they hog the CPU (such as `usvfs`) or because they have dependencies that have to be built first.
 If any task fails to build, all the active tasks are aborted as quickly as possible.
@@ -301,7 +236,7 @@ If any task fails to build, all the active tasks are aborted as quickly as possi
 Each task has a name, some have more. MO tasks for example have a full name that corresponds to their git repo (such as `modorganizer-game_features`) and a shorter name (such as `game_features`). Both can be used interchangeably. The task name can also be `super`, which refers to all repos hosted on the Mod Organizer Github account, minus `libbsarch`, `usvfs` and `NexusClientCli`. Globs can be used, like `installer_*`. See `mob list` for a list of all available tasks.
-#### Options for `build`
+#### Options
 | Option | Description |
 | ---    | --- |
@@ -310,78 +245,75 @@ Each task has a name, some have more. MO tasks for example have a full name that
 | `--reconfigure`                      | Reconfigures the task by running cmake, configure scripts, etc. Some tasks might have to delete the whole source directory. |
 | `--rebuild`                          | Cleans and rebuilds projects. Some tasks might have to delete the whole source directory |
 | `--new`                              | Implies all the four flags above. |
-| `--clean-task`, `--no-clean-task` | Sets whether tasks are cleaned. With `--no-clean-task`, the flags above are ignored. |
+| `--clean-task`,<br>`--no-clean-task` | Sets whether tasks are cleaned. With `--no-clean-task`, the flags above are ignored. |
-| `--fetch-task`, `--no-fetch-task` | Sets whether tasks are fetched. With `--no-fetch-task`, nothing is downloaded, extracted, cloned or pulled. |
+| `--fetch-task`,<br>`--no-fetch-task` | Sets whether tasks are fetched. With `--no-fetch-task`, nothing is downloaded, extracted, cloned or pulled. |
-| `--build-task`, `--no-build-task` | Sets whether tasks are built. With `--no-build-task`, nothing is ever built or installed. |
+| `--build-task`,<br>`--no-build-task` | Sets whether tasks are built. With `--no-build-task`, nothing is ever built or installed. |
-| `--pull`, `--no-pull`             | For repos that are controlled by git, whether to pull repos that are already cloned. With `--no-pull`, once a repo is cloned, it is never updated automatically. |
+| `--pull`,<br>`--no-pull`             | For repos that are controlled by git, whether to pull repos that are already cloned. With `--no-pull`, once a repo is cloned, it is never updated automatically. |
-| `--revert-ts`, `--no-revert-ts`   | Most projects will generate `.ts` files for translations. These files are typically not committed to Github and so will often conflict when trying to pull. With `--revert-ts`, any `.ts` file is reverted before pulling. |
+| `--revert-ts`,<br>`--no-revert-ts`   | Most projects will generate `.ts` files for translations. These files are typically not committed to Github and so will often conflict when trying to pull. With `--revert-ts`, any `.ts` file is reverted before pulling. |
 | `--ignore-uncommitted-changes`       | With `--reextract`, ignores repos that have uncommitted changes and deletes the directory without confirmation. |
 | `--keep-msbuild`                     | `mob` starts a lot of `msbuild.exe` processes, some of which hold locks on the build directory. Because that's pretty darn annoying, `mob` will kill all `msbuild.exe` processes when it finished, unless this flag is given. |
 | `<task>...`                          | List of tasks to run, see [Task names](#task-names). |
 ### `list`
 ### `list`
 Lists all the available task names. If a task has multiple names, they are all shown, separated by a comma.
-#### Options for `list`
+#### Options
 | Option | Description |
 | --- | --- |
 | `--all`     | Shows a task tree to see which are built in parallel. |
 | `<task>...` | This is the same list of tasks that can be given in the `build` command. With `--all`, this will only show the tasks that would be built. |
 ### `options`
 ### `options`
 Lists all the options after parsing the INIs and the command line.
 ### `release`
 Creates a release in `prefix/releases`. Only supports devbuilds for now. A release is made out of three archives:
-
+ - Binaries from `prefix/install/bin`;
- Binaries from `prefix/install/bin`;
+ - PDBs from `prefix/install/pdb`;
- PDBs from `prefix/install/pdb`;
+ - Sources from various directories in `prefix/build`.
 - Sources from various directories in `prefix/build`.
 The archive filename is `Mod.Organizer-version-suffix-what.7z`, where:
 - `version` is taken from `ModOrganizer.exe`, `version.rc` or from `--version`;
 - `suffix` is the optional `--suffix` argument;
 - `what` is either nothing, `src` or `pdbs`.
 - `version` is taken from `ModOrganizer.exe`, `version.rc` or from `--version`;
 - `suffix` is the optional `--suffix` argument;
 - `what` is either nothing, `src` or `pdbs`.
 #### Options for `release`
 #### Options
 | Option | Description |
 | --- | --- |
-| `--bin`, `--no-bin`   | Whether the binary archive is created [default: yes] |
+| `--bin`,<br>`--no-bin`   | Whether the binary archive is created [default: yes] |
-| `--pdbs`, `--no-pdbs` | Whether the PDBs archive is created [default: yes] |
+| `--pdbs`,<br>`--no-pdbs` | Whether the PDBs archive is created [default: yes] |
-| `--src`,, `--no-src`   | Whether the source archive is created [default: yes] |
+| `--src`,<br>`--no-src`   | Whether the source archive is created [default: yes] |
 | `--version-from-exe`     | Retrieves version information from ModOrganizer.exe [default] |
 | `--version-from-rc`      | Retrieves version information from `modorganizer/src/version.rc` |
 | `--rc <PATH>`            | Overrides the path to `version.rc` |
 | `--version <VERSION>`    | Overrides the version string, ignores `--version-from-exe` and `--version-from-rc` |
 | `--output-dir <PATH>`    | Sets the output directory to use instead of `prefix/releases` |
-| `--suffix <SUFFIX>`      | Optional suffix to add to the archive filenames. |
+| `--suffix <SUFFIX>`      | Optional suffix to add to the archive filenames
 | `--force`                | `mob` will refuse to create a source archive over 20MB because it would probably be incorrect. This ignores the file size warnings and creates the archive regardless of its size. |
 ### `git`
 ### `git`
 Various commands to manage the git repos. Includes `usvfs`, `NexusClientCli` and all the projects under `modorganizer_super`.
 #### `set-remotes`
 Does the same thing as the when `set_origin_remotes` is set in the INI: renames `origin` to `upstream` and adds a new `origin` with the options below. See [Origin and upstream remotes](#origin-and-upstream-remotes).
 | Option | Description |
 | --- | --- |
-| `--username <USERNAME>` | Git username. |
+| `--username <USERNAME>` | Git username |
-| `--email <EMAIL>`       | Git email. |
+| `--email <EMAIL>`       | Git email |
-| `--key <PATH>`          | Path to a putty key. |
+| `--key <PATH>`          | Path to a putty key |
-| `--no-push`             | Disables pushing to `upstream` by changing the push url to `nopushurl` to avoid accidental pushes. |
+| `--no-push`             | Disables pushing to `upstream` by changing the push url to `nopushurl` to avoid accidental pushes |
-| `--push-origin`         | Sets the new `origin` remote as the default push target. |
+| `--push-origin`         | Sets the new `origin` remote as the default push target
-| `<path>`                | Only use this repo instead of going through all of them. |
+| `<path>`                | Only use this repo instead of going through all of them |
 #### `add-remote`
 Simply adds a new remote with the given parameters to all the git repos.
 | Option | Description |
@@ -392,22 +324,31 @@ Simply adds a new remote with the given parameters to all the git repos.
 | `--push-origin`         | Sets this new remote as the default push target |
 | `<path>`                | Only use this repo instead of going through all of them |
 ### `cmake-config`
-The `cmake-config` command can display the `CMAKE_INSTALL_PREFIX` and
+### `cmake`
-`CMAKE_PREFIX_PATH` variable using by `mob` itself when building so that you can run
+Runs `cmake` in a directory, as if `mob` had done it as part of the build process for a `modorganizer` project. The `cmake` invocation will contain all variables required for `cmake_common` to work.
 your own `cmake`.
-Below is a typical use of the command:
+By default, this runs:
-
+```
-```powershell
+cmake
-# configure the current project with preset vs2022-windows using mob PATH
+  -G "Visual Studio version year"
-cmake --preset vs2022-windows `
+  -A x64
-  ("-DCMAKE_INSTALL_PREFIX=" + (mob cmake-config install-prefix)) `
+  -DCMAKE_BUILD_TYPE=Release
-  ("-DCMAKE_PREFIX_PATH=" + (mob cmake-config prefix-path))
+  -DCMAKE_INSTALL_MESSAGE=NEVER
  <all defines>
  --log-level=ERROR
  --no-warn-unused-cli
  ..
 ```
-### `inis`
+#### Options
 | Option | Description |
 | --- | --- |
 | `--generator <GEN>` | Sets the `-G` option |
 | `--cmd` | Sets the last bit of the command, defaults to `..` |
 | `--x86`, `--x64` | Whether to use the 32-bit or 64-bit vcvars. If `--generator` is not given, also sets `-A`. |
 | `--install-prefix <PATH>` | Passes `-DCMAKE_INSTALL_PREFIX=<path>` to cmake |
-Shows a list of the all the INIs that would be loaded, in order of priority.
+
-See [INI files](#override-options-using-ini-files).
+### `inis`
 Shows a list of the all the INIs that would be loaded, in order of priority. See [INI files](#ini-files).
@@ -0,0 +1,9 @@
 param(
    [Parameter(Mandatory = $true)][String]$Path,
    [Parameter(Mandatory = $true)][String]$Output
 )
 7z a $Output (Join-Path -Path $Path -ChildPath "boost")
 7z a $Output (Join-Path -Path $Path -ChildPath "lib32-msvc-14.3")
 7z a $Output (Join-Path -Path $Path -ChildPath "lib64-msvc-14.3")
 7z a $Output (Join-Path -Path $Path -ChildPath "LICENSE_1_0.txt")
--- a/Show More
+++ b/Show More