diff options
| author | Jay Kwak <82421531+jkwak-work@users.noreply.github.com> | 2024-10-25 21:12:37 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-25 21:12:37 -0700 |
| commit | a508b264eda4bc3c99ba1f44eab1dec6e5ce06c0 (patch) | |
| tree | 717722aefcae6b2a5adbccfbcd8aece4ed81f0b7 /docs/user-guide/a1-03-obfuscation.md | |
| parent | 49c691e86862d092cd389a02beb4003ee59a4417 (diff) | |
Swap the term StdLib with Core-Module or Standard-Module in documents (#5414)
This PR is limited to documents.
All use of "Standard library" or "StdLib" are replaced with either "core module" or "standard modules", depending on the context.
Diffstat (limited to 'docs/user-guide/a1-03-obfuscation.md')
| -rw-r--r-- | docs/user-guide/a1-03-obfuscation.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/user-guide/a1-03-obfuscation.md b/docs/user-guide/a1-03-obfuscation.md index abce92e12..dab216940 100644 --- a/docs/user-guide/a1-03-obfuscation.md +++ b/docs/user-guide/a1-03-obfuscation.md @@ -169,13 +169,13 @@ slangc module-source.slang -o module.zip -g -obfuscate This will compile "module-source.slang" into SlangIR module (aka `slang-module`) and places the `.slang-module` inside of the zip. As obfuscation is enabled the .zip will also contain the obfuscated source map for the module. -The `.zip` file can now be used and referenced as a library +The `.zip` file can now be used and referenced as a module ``` slangc source.slang -target dxil -stage compute -entry computeMain -obfuscate -r module.zip ``` -Notice here that the `-r` library reference is to the `.zip` file rather than the more usual `.slang-module` that is contained in the zip file. By referencing the library in this way Slang will automatically associate the contained obfuscated source map with the module. It will use that mapping for outputting diagnostics. +Notice here that the `-r` module reference is to the `.zip` file rather than the more usual `.slang-module` that is contained in the zip file. By referencing the module in this way Slang will automatically associate the contained obfuscated source map with the module. It will use that mapping for outputting diagnostics. It is also worth noticing that in this second compilation, using `module.zip`, we need the `-obfuscate` flag set. If this isn't set linking will not work correctly. @@ -256,7 +256,7 @@ Why you might not want to use an emit source map * The `#line` mechanism doesn't require any special handling, and the mapping back is embedded directly into the emitted source/output binary * There is more housekeeping in getting keeping and using source maps * Currently Slang doesn't directly expose a source map processing API directly - * We do support source maps in library files, or produced as part of a compilation + * We do support source maps in module files, or produced as part of a compilation * A developer could use the slang `compiler-core` implementation * In the future the project could provide some API support |