CiCi Cam — Qt 6.9.3 corresponding source and library replacement
================================================================

Qt is installed using the Qt Maintenance Tool and distributed as unmodified,
dynamically linked libraries. You do not need the proprietary CiCi Cam source
code to replace interface-compatible Qt shared libraries.

Corresponding source downloads:
https://cici-cam.com/open-source/#qt-source

The source packages are hosted at:
https://static.cici-cam.com/download/opensource/qt/6.9.3/

Download the individually linked qtbase, qtsvg, qtimageformats and
qttranslations archives from the page, along with qt-6.9.3-build-metadata.zip.
The source archives include their bundled dependencies and build scripts.
The metadata archive contains the Windows installation's original configure
options, build summaries and SPDX bills of materials. SHA-256 checksums and
source revisions are recorded in sources.json beside this document.
CiCi Cam makes no modifications to the Qt source code.

Qt's own source release includes modules and tools with different licenses.
Their inclusion in a source archive does not mean they are linked into CiCi Cam.
Use the LGPL/permissive alternatives for the runtime components where provided;
in particular use the FreeType Project License (FTL) for FreeType.

Windows (x64)
-------------
1. Keep a backup of the installed CiCi Cam directory and close CiCi Cam.
2. Obtain the source archives above. Use an x64 Visual Studio 2022 developer
   environment with the matching C++ runtime, CMake and Ninja. Qt's build
   requirements and configure options are documented at:
   https://doc.qt.io/qt-6.9/windows-building.html
3. Build shared Qt libraries, keeping the ABI, architecture and build mode
   compatible with the installed application. The recorded configure files
   provide the original Qt settings; machine-specific build paths may be
   changed. Build qtbase first, install it, then configure qtsvg and
   qtimageformats against that Qt installation with qt-configure-module.
4. Replace Qt6Core.dll, Qt6Gui.dll, Qt6Widgets.dll and Qt6Svg.dll alongside
   cicicam.exe with the rebuilt, compatible versions. Replace matching
   plugins/platforms/qwindows.dll and plugins/imageformats/*.dll as needed.
   Keep dependent Qt DLLs/plugins from the same build together. Debug builds
   use the d-suffixed DLL and plugin names instead.
5. Start cicicam.exe. Administrator permission may be required to change files
   in Program Files. Restore the backed-up files to undo the replacement.

macOS (Apple Silicon)
--------------------
Qt frameworks and plugins are under cicicam.app/Contents/Frameworks and
Contents/PlugIns. Inspect the actual bundle paths before replacing files.
Build shared Qt for arm64 and macOS 14 or later with a compatible ABI:
https://doc.qt.io/qt-6.9/macos-building.html

Replacing a signed framework changes the bundle signature. The modified copy
may require local re-signing and OS approval. Preserve the virtual-camera
system extension, its identity and provisioning information. Do not assume
that replacing a framework alone bypasses macOS signature or entitlement rules.
Contact service@cici-cam.com for assistance with the installation information
needed for your release/channel, including library replacement on macOS.

License rights
--------------
Modification of Qt and reverse engineering to debug those modifications are
permitted under LGPLv3. Any conflicting restriction in the CiCi Cam terms does
not apply to these rights. Support or warranty for user-modified binaries is
not promised. These permissions do not change the license of CiCi Cam itself.

See LGPL-3.0.txt, GPL-3.0.txt and THIRD-PARTY-NOTICES.txt for the license texts.
