docs: clarify licensing and macOS backend status

Add a root license notice, move the MIT text under `LICENSES/`, and update install/packaging paths so distributed artifacts still include the expected license files. Refresh README and docs to better describe the current macOS CoreGraphics-only keyboard/mouse backend and keep planned native virtual-HID gamepad support scoped separately.

Author: ReenigneArcher

CMakeLists.txt

@@ -170,8 +170,9 @@ if(LIBVIRTUALHID_INSTALL)
           "find_dependency(X11 COMPONENTS Xtst)\n")
     endif()
 
-    install(FILES "${CMAKE_CURRENT_SOURCE_DIR}/LICENSE"
+    install(FILES "${CMAKE_CURRENT_SOURCE_DIR}/LICENSES/MIT.md"
       DESTINATION "${CMAKE_INSTALL_DATADIR}/licenses/libvirtualhid"
+      RENAME LICENSE
       COMPONENT library)
 
     configure_package_config_file(

LICENSE.md

@@ -0,0 +1,14 @@
+# Repository License Notice
+
+`libvirtualhid` contains components under different licenses. This file is a
+summary and does not replace the complete license texts.
+
+- The cross-platform library source, public headers, non-driver backends,
+  examples, tests, build scripts, and documentation are licensed under the
+  [MIT License](LICENSES/MIT.md), except where the license map says otherwise.
+- The Windows UMDF driver, broker, proprietary entitlement and evaluation
+  sources, and generated Windows driver package artifacts are licensed under
+  the [LizardByte Source-Available License 1.0](LICENSES/LicenseRef-LizardByte-SAL-1.0.md).
+
+See the [license map](LICENSES/README.md) for the authoritative repository path
+and artifact assignments.

LICENSE LICENSES/MIT.mdLICENSE renamed to LICENSES/MIT.md

@@ -6,7 +6,7 @@ Windows driver package.
 - LB-SAL 1.0 SPDX custom identifier: `LicenseRef-LizardByte-SAL-1.0`.
 - Cross-platform library source, public headers, non-driver backends, examples,
   tests, build scripts, and documentation unless listed below:
-  [MIT](https://github.com/LizardByte/libvirtualhid/blob/master/LICENSE).
+  [MIT](https://github.com/LizardByte/libvirtualhid/blob/master/LICENSES/MIT.md).
 - Windows UMDF driver source under `src/platform/windows/driver/`, the broker
   service under `src/platform/windows/broker/`, and the broker entitlement and
   evaluation sources

LICENSES/README.md

@@ -109,10 +109,12 @@ devices from the OS, or ship a Windows kernel-mode driver.
 
 ## 📌 Status
 
-Linux and Windows are the active backends. Linux uses standard user-space kernel
-interfaces. Windows remains user-mode: the C++ library talks to a UMDF2 control
-driver, and the driver publishes HID gamepads through VHF. macOS support is not
-implemented yet.
+Linux and Windows provide virtual-device backends. Linux uses standard
+user-space kernel interfaces. Windows remains user-mode: the C++ library talks
+to a UMDF2 control driver, and the driver publishes HID gamepads through VHF.
+macOS currently provides a limited CoreGraphics synthetic-input backend for
+keyboard and mouse only. It is not a virtual-HID backend and does not yet
+support gamepads; native macOS virtual-HID gamepad support is planned.
 
 The library is designed around gamepad use first because remote streaming hosts
 are the first consumer class. Non-gamepad device types are available through the
@@ -183,8 +185,12 @@ test app path and does not currently advertise an ARM64 build.
 
 ## 📄 License
 
-The cross-platform `libvirtualhid` library is licensed under the MIT License.
+The cross-platform `libvirtualhid` library is licensed under the
+[MIT License](LICENSES/MIT.md).
 The Windows UMDF driver, broker, proprietary entitlement/evaluation sources,
 and generated Windows driver package artifacts, including the driver MSI, are
-licensed under the LizardByte Source-Available License 1.0 (LB-SAL 1.0). See the
-[license map](LICENSES/README.md) for the full repository split.
+licensed under the
+[LizardByte Source-Available License 1.0](LICENSES/LicenseRef-LizardByte-SAL-1.0.md)
+(LB-SAL 1.0). The root [license notice](LICENSE.md) points to both complete license
+texts; see the [license map](LICENSES/README.md) for the authoritative repository
+path and artifact assignments.

README.md

@@ -10,7 +10,7 @@ set(CPACK_PACKAGE_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/cpack_artifacts)
 set(CPACK_PACKAGE_CONTACT "https://app.lizardbyte.dev")
 set(CPACK_PACKAGE_DESCRIPTION ${CMAKE_PROJECT_DESCRIPTION})
 set(CPACK_PACKAGE_HOMEPAGE_URL ${CMAKE_PROJECT_HOMEPAGE_URL})
-set(CPACK_RESOURCE_FILE_LICENSE ${PROJECT_SOURCE_DIR}/LICENSE)
+set(CPACK_RESOURCE_FILE_LICENSE ${PROJECT_SOURCE_DIR}/LICENSES/MIT.md)
 set(CPACK_PACKAGE_FILE_NAME "${CMAKE_PROJECT_NAME}")
 set(CPACK_STRIP_FILES YES)
 

cmake/packaging/common.cmake

@@ -56,10 +56,14 @@ if(LIBVIRTUALHID_DRIVER_TEST_CERTIFICATE)
       OPTIONAL)
 endif()
 
-install(FILES
-        "${PROJECT_SOURCE_DIR}/LICENSE"
-        "${LIBVIRTUALHID_DRIVER_LICENSE_FILE}"
+install(FILES "${PROJECT_SOURCE_DIR}/LICENSES/MIT.md"
+  DESTINATION "licenses"
+  RENAME "MIT.md"
+  COMPONENT driver)
+
+install(FILES "${LIBVIRTUALHID_DRIVER_LICENSE_FILE}"
   DESTINATION "licenses"
+  RENAME "LicenseRef-LizardByte-SAL-1.0.md"
   COMPONENT driver)
 
 set(CPACK_COMPONENT_DRIVER_DISPLAY_NAME "Windows UMDF Driver")

cmake/packaging/windows.cmake

@@ -94,6 +94,6 @@ code and tests provide a better source of truth.
   libvirtualhid driver-package checks.
 - Validate Linux host-adapter behavior across the selected controller profiles.
 - Define and implement the FreeBSD-supported backend subset.
-- Extend macOS support beyond CoreGraphics keyboard and mouse injection to
-  native virtual HID devices, including signing, entitlement, and installer
-  constraints.
+- Add native macOS virtual-HID gamepad support beyond the current CoreGraphics
+  keyboard and mouse injection backend, including signing, entitlement, and
+  installer constraints.

docs/development.md

@@ -272,6 +272,7 @@ Unsupported macOS capabilities currently return `unsupported_profile`:
 - Touchscreen, trackpad, and pen tablet devices.
 - Keyboard text input through `KeyboardTextEvent`.
 
-Future native virtual HID support may use `IOHIDUserDevice`,
-DriverKit/HIDDriverKit, or a combination that preserves the same public API
-while documenting any signing, entitlement, and installer requirements.
+Native macOS virtual-HID gamepad support is planned. A future backend may use
+`IOHIDUserDevice`, DriverKit/HIDDriverKit, or a combination that preserves the
+same public API while documenting any signing, entitlement, and installer
+requirements.

docs/platform-support.md

@@ -72,5 +72,5 @@ Remaining replacement work is validation and packaging, not broad API shape:
 - Evaluate an optional FreeBSD CUSE-backed `uhid(4)`-compatible device for
   direct HID consumers. This would supplement uinput; it is not equivalent to
   registering a virtual device with FreeBSD's kernel HID bus.
-- Validate macOS CoreGraphics keyboard and mouse support in a streaming host, and
-  keep native macOS virtual HID device work scoped separately.
+- Validate macOS CoreGraphics keyboard and mouse support in a streaming host,
+  and keep the planned native macOS virtual-HID gamepad work scoped separately.