docs: explain Windows module DLL lookup - #95
Merged
Merged
Conversation
📊 Tutorial execution reportsRendered tutorial alongside the commands actually run and their output (updated each run, commit
Pages can take a minute to update after the run finishes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document how the dedicated Windows module host makes DLLs beside a module available to later runtime loads. The guide explains which directories are searched, the packaging requirement, and why existing module-side workarounds must remain until the updated host is deployed.
This documentation accompanies logos-module-loader-qt #20. Linux and macOS packaging guidance is unchanged.
Validation: checked the guidance against the host implementation and passed whitespace checks.