From 941b834f3ba15eba9bfa80eb370077ec9c845efd Mon Sep 17 00:00:00 2001 From: Tim Foley Date: Tue, 25 Jul 2017 16:21:23 -0700 Subject: Add a `-o` option to command-line `slangc` Fixes #11 - This adds a `-o` command-line option for specifying an output file. - The code tries to be a bit smart, to glean an output format from a file extension, and also to associate multiple `-o` options with multiple `-entry` options if needed. - There is a restriction that all the output files need to agree on the code generation target. This is reasonable for now, but might be something to lift eventualy - There is a restriction that only one output file is allowed per entry point - Together with the previous item this means you can't output both a `.spv` and a `.spv.asm` in one pass, even though both should be possible - There is currently a restriction that output paths only apply to entry points - This means there is no way to output reflection JSON to a file with `-o` (but that is mostly just a debugging feature for now) - This also means we don't support any "container" formats that can encapsulate multiple compiled entry points --- source/slang/slang.cpp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'source/slang/slang.cpp') diff --git a/source/slang/slang.cpp b/source/slang/slang.cpp index 65f12fe59..bb83eb8af 100644 --- a/source/slang/slang.cpp +++ b/source/slang/slang.cpp @@ -684,6 +684,12 @@ SLANG_API void spSetLineDirectiveMode( REQ(request)->lineDirectiveMode = Slang::LineDirectiveMode(mode); } +SLANG_API void spSetCommandLineCompilerMode( + SlangCompileRequest* request) +{ + REQ(request)->isCommandLineCompile = true; + +} SLANG_API void spSetCodeGenTarget( SlangCompileRequest* request, -- cgit v1.2.3