diff options
Diffstat (limited to 'docs/user-guide/08-compiling.md')
| -rw-r--r-- | docs/user-guide/08-compiling.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/user-guide/08-compiling.md b/docs/user-guide/08-compiling.md index 623a3111f..8fd94ff3c 100644 --- a/docs/user-guide/08-compiling.md +++ b/docs/user-guide/08-compiling.md @@ -266,19 +266,19 @@ The `slangc` compiler provides a few conveniences for command-line compilation: You can compile a `.slang` file into a binary IR module. For example, given the following source: ```hlsl -// library.slang +// my_library.slang float myLibFunc() { return 5.0; } ``` -You can compile it into `library.slang-module` with the following slangc command line: +You can compile it into `my_library.slang-module` with the following slangc command line: ```bat -slangc library.slang -o library.slang-module +slangc my_library.slang -o my_library.slang-module ``` -This allows you to deploy just the `library.slang-module` file to users of the library, and it can be consumed in the user code with the same `import` syntax: +This allows you to deploy just the `my_library.slang-module` file to users of the module, and it can be consumed in the user code with the same `import` syntax: ```hlsl -import library; +import my_library; ``` ### More Options @@ -329,8 +329,8 @@ Slang::ComPtr<IGlobalSession> globalSession; createGlobalSession(globalSession.writeRef()); ``` -When a global session is created, the Slang system will load its internal representation of the _standard library_ that the compiler provides to user code. -The standard library can take a significant amount of time to load, so applications are advised to use a single global session if possible, rather than creating and then disposing of one for each compile. +When a global session is created, the Slang system will load its internal representation of the _core module_ that the compiler provides to user code. +The core module can take a significant amount of time to load, so applications are advised to use a single global session if possible, rather than creating and then disposing of one for each compile. > #### Note #### > Currently, the global session type is *not* thread-safe. @@ -611,8 +611,8 @@ The only functions which are currently thread safe are ```C++ SlangSession* spCreateSession(const char* deprecated); SlangResult slang_createGlobalSession(SlangInt apiVersion, slang::IGlobalSession** outGlobalSession); -SlangResult slang_createGlobalSessionWithoutStdLib(SlangInt apiVersion, slang::IGlobalSession** outGlobalSession); -ISlangBlob* slang_getEmbeddedStdLib(); +SlangResult slang_createGlobalSessionWithoutCoreModule(SlangInt apiVersion, slang::IGlobalSession** outGlobalSession); +ISlangBlob* slang_getEmbeddedCoreModule(); SlangResult slang::createGlobalSession(slang::IGlobalSession** outGlobalSession); const char* spGetBuildTagString(); ``` |