llvm-mirror/tools/llvm-cvtres/Opts.td

include "llvm/Option/OptParser.td"

// All the switches can be preceded by either '/' or '-'.

def DEFINE : Joined<["/", "-"], "DEFINE:">, HelpText<"">, MetaVarName<"symbol">;
def FOLDDUPS : Flag<["/", "-"], "FOLDDUPS:">, HelpText<"">;
def MACHINE : Joined<["/", "-"], "MACHINE:">, HelpText<"">, MetaVarName<"{ARM|ARM64|EBC|IA64|X64|X86}">;
def NOLOGO : Flag<["/", "-"], "NOLOGO">, HelpText<"">;
def OUT : Joined<["/", "-"], "OUT:">, HelpText<"">, MetaVarName<"filename">;
def READONLY : Flag<["/", "-"], "READONLY">, HelpText<"">;
def VERBOSE : Flag<["/", "-"], "VERBOSE">, HelpText<"">;
def HELP : Flag<["/", "-"], "HELP">;
def H : Flag<["/", "-"], "H">, Alias<HELP>;
def HELP_Q : Flag<["/?", "-?"], "">, Alias<HELP>;

// Extensions.

def TIMESTAMP : Joined<["/", "-"], "TIMESTAMP:">,
    HelpText<"Timestamp for coff header, defaults to current time">;
Add empty shell of llvm-cvtres. This marks the beginning of an effort to port remaining MSVC toolchain miscellaneous utilities to all platforms. Currently clang-cl shells out to certain additional tools such as the IDL compiler, resource compiler, and a few other tools, but as these tools are Windows-only it limits the ability of clang to target Windows on other platforms. having a full suite of these tools directly in LLVM should eliminate this constraint. The current implementation provides no actual functionality, it is just an empty skeleton executable for the purposes of making incremental changes. Differential Revision: https://reviews.llvm.org/D32095 Patch by Eric Beckmann (ecbeckmann@google.com) llvm-svn: 301004 2017-04-21 19:30:29 +02:00			`include "llvm/Option/OptParser.td"`

[llvm-cvtres] Allow parameters preceded by '-' in addition to '/' The real cvtres.exe also allows parameters in either form. Differential Revision: https://reviews.llvm.org/D46358 llvm-svn: 331402 2018-05-02 23:15:13 +02:00			`// All the switches can be preceded by either '/' or '-'.`

			`def DEFINE : Joined<["/", "-"], "DEFINE:">, HelpText<"">, MetaVarName<"symbol">;`
			`def FOLDDUPS : Flag<["/", "-"], "FOLDDUPS:">, HelpText<"">;`
			`def MACHINE : Joined<["/", "-"], "MACHINE:">, HelpText<"">, MetaVarName<"{ARM\|ARM64\|EBC\|IA64\|X64\|X86}">;`
			`def NOLOGO : Flag<["/", "-"], "NOLOGO">, HelpText<"">;`
			`def OUT : Joined<["/", "-"], "OUT:">, HelpText<"">, MetaVarName<"filename">;`
			`def READONLY : Flag<["/", "-"], "READONLY">, HelpText<"">;`
			`def VERBOSE : Flag<["/", "-"], "VERBOSE">, HelpText<"">;`
			`def HELP : Flag<["/", "-"], "HELP">;`
			`def H : Flag<["/", "-"], "H">, Alias<HELP>;`
llvm-cvtres: Accept /? as help flag, like cvtres.exe llvm-svn: 359064 2019-04-24 04:11:24 +02:00			`def HELP_Q : Flag<["/?", "-?"], "">, Alias<HELP>;`
Let writeWindowsResourceCOFF() take a TimeStamp parameter For lld, pass in Config->Timestamp (which is set based on lld's /timestamp: and /Brepro flags). Since the writeWindowsResourceCOFF() data is only used in-memory by LLD and the obj's timestamp isn't used for anything in the output, this doesn't change behavior. For llvm-cvtres, add an optional /timestamp: parameter, and use the current behavior of calling time() if the parameter is not passed in. This doesn't really change observable behavior (unless someone passes /timestamp: to llvm-cvtres, which wasn't possible before), but it removes the last unqualified call to time() from llvm/lib, which seems like a good thing. Differential Revision: https://reviews.llvm.org/D63116 llvm-svn: 363050 2019-06-11 13:26:50 +02:00
			`// Extensions.`

			`def TIMESTAMP : Joined<["/", "-"], "TIMESTAMP:">,`
			`HelpText<"Timestamp for coff header, defaults to current time">;`