2017-08-10 18:21:44 +02:00
|
|
|
//===-- llvm-rc.cpp - Compile .rc scripts into .res -------------*- C++ -*-===//
|
2017-07-25 02:25:18 +02:00
|
|
|
//
|
2019-01-19 09:50:56 +01:00
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
2017-07-25 02:25:18 +02:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// Compile .rc scripts into .res files. This is intended to be a
|
|
|
|
// platform-independent port of Microsoft's rc.exe tool.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2017-09-29 19:14:09 +02:00
|
|
|
#include "ResourceFileWriter.h"
|
2018-05-09 20:21:03 +02:00
|
|
|
#include "ResourceScriptCppFilter.h"
|
2017-08-18 20:24:17 +02:00
|
|
|
#include "ResourceScriptParser.h"
|
2017-09-29 19:14:09 +02:00
|
|
|
#include "ResourceScriptStmt.h"
|
|
|
|
#include "ResourceScriptToken.h"
|
2017-08-10 18:21:44 +02:00
|
|
|
|
2021-04-14 15:24:30 +02:00
|
|
|
#include "llvm/ADT/Triple.h"
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
#include "llvm/Object/WindowsResource.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Option/Arg.h"
|
|
|
|
#include "llvm/Option/ArgList.h"
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
#include "llvm/Support/CommandLine.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Support/Error.h"
|
2017-09-29 19:14:09 +02:00
|
|
|
#include "llvm/Support/FileSystem.h"
|
2021-04-14 15:24:30 +02:00
|
|
|
#include "llvm/Support/FileUtilities.h"
|
|
|
|
#include "llvm/Support/Host.h"
|
2018-04-13 20:26:06 +02:00
|
|
|
#include "llvm/Support/InitLLVM.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Support/ManagedStatic.h"
|
2017-11-17 02:00:35 +01:00
|
|
|
#include "llvm/Support/MemoryBuffer.h"
|
2018-05-02 23:15:24 +02:00
|
|
|
#include "llvm/Support/Path.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Support/PrettyStackTrace.h"
|
|
|
|
#include "llvm/Support/Process.h"
|
2021-04-14 15:24:30 +02:00
|
|
|
#include "llvm/Support/Program.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Support/Signals.h"
|
2021-04-14 15:24:30 +02:00
|
|
|
#include "llvm/Support/StringSaver.h"
|
2017-07-25 02:25:18 +02:00
|
|
|
#include "llvm/Support/raw_ostream.h"
|
|
|
|
|
2019-01-16 09:09:22 +01:00
|
|
|
#include <algorithm>
|
2017-07-25 02:25:18 +02:00
|
|
|
#include <system_error>
|
|
|
|
|
|
|
|
using namespace llvm;
|
2017-09-29 19:14:09 +02:00
|
|
|
using namespace llvm::rc;
|
2017-07-25 02:25:18 +02:00
|
|
|
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
// Input options tables.
|
|
|
|
|
|
|
|
enum ID {
|
|
|
|
OPT_INVALID = 0, // This is not a correct option ID.
|
|
|
|
#define OPTION(PREFIX, NAME, ID, KIND, GROUP, ALIAS, ALIASARGS, FLAGS, PARAM, \
|
|
|
|
HELPTEXT, METAVAR, VALUES) \
|
|
|
|
OPT_##ID,
|
|
|
|
#include "Opts.inc"
|
|
|
|
#undef OPTION
|
|
|
|
};
|
|
|
|
|
|
|
|
#define PREFIX(NAME, VALUE) const char *const NAME[] = VALUE;
|
|
|
|
#include "Opts.inc"
|
|
|
|
#undef PREFIX
|
|
|
|
|
|
|
|
static const opt::OptTable::Info InfoTable[] = {
|
|
|
|
#define OPTION(PREFIX, NAME, ID, KIND, GROUP, ALIAS, ALIASARGS, FLAGS, PARAM, \
|
|
|
|
HELPTEXT, METAVAR, VALUES) \
|
|
|
|
{ \
|
|
|
|
PREFIX, NAME, HELPTEXT, \
|
|
|
|
METAVAR, OPT_##ID, opt::Option::KIND##Class, \
|
|
|
|
PARAM, FLAGS, OPT_##GROUP, \
|
|
|
|
OPT_##ALIAS, ALIASARGS, VALUES},
|
|
|
|
#include "Opts.inc"
|
|
|
|
#undef OPTION
|
|
|
|
};
|
|
|
|
|
|
|
|
class RcOptTable : public opt::OptTable {
|
|
|
|
public:
|
|
|
|
RcOptTable() : OptTable(InfoTable, /* IgnoreCase = */ true) {}
|
|
|
|
};
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
enum Windres_ID {
|
|
|
|
WINDRES_INVALID = 0, // This is not a correct option ID.
|
|
|
|
#define OPTION(PREFIX, NAME, ID, KIND, GROUP, ALIAS, ALIASARGS, FLAGS, PARAM, \
|
|
|
|
HELPTEXT, METAVAR, VALUES) \
|
|
|
|
WINDRES_##ID,
|
|
|
|
#include "WindresOpts.inc"
|
|
|
|
#undef OPTION
|
|
|
|
};
|
|
|
|
|
|
|
|
#define PREFIX(NAME, VALUE) const char *const WINDRES_##NAME[] = VALUE;
|
|
|
|
#include "WindresOpts.inc"
|
|
|
|
#undef PREFIX
|
|
|
|
|
|
|
|
static const opt::OptTable::Info WindresInfoTable[] = {
|
|
|
|
#define OPTION(PREFIX, NAME, ID, KIND, GROUP, ALIAS, ALIASARGS, FLAGS, PARAM, \
|
|
|
|
HELPTEXT, METAVAR, VALUES) \
|
|
|
|
{ \
|
|
|
|
WINDRES_##PREFIX, NAME, HELPTEXT, \
|
|
|
|
METAVAR, WINDRES_##ID, opt::Option::KIND##Class, \
|
|
|
|
PARAM, FLAGS, WINDRES_##GROUP, \
|
|
|
|
WINDRES_##ALIAS, ALIASARGS, VALUES},
|
|
|
|
#include "WindresOpts.inc"
|
|
|
|
#undef OPTION
|
|
|
|
};
|
|
|
|
|
|
|
|
class WindresOptTable : public opt::OptTable {
|
|
|
|
public:
|
|
|
|
WindresOptTable() : OptTable(WindresInfoTable, /* IgnoreCase = */ false) {}
|
|
|
|
};
|
|
|
|
|
2017-07-25 02:25:18 +02:00
|
|
|
static ExitOnError ExitOnErr;
|
2021-04-14 15:24:30 +02:00
|
|
|
static FileRemover TempPreprocFile;
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
static FileRemover TempResFile;
|
2017-08-10 18:21:44 +02:00
|
|
|
|
2017-10-11 22:12:09 +02:00
|
|
|
LLVM_ATTRIBUTE_NORETURN static void fatalError(const Twine &Message) {
|
2017-08-10 18:21:44 +02:00
|
|
|
errs() << Message << "\n";
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
2021-04-14 15:24:30 +02:00
|
|
|
std::string createTempFile(const Twine &Prefix, StringRef Suffix) {
|
|
|
|
std::error_code EC;
|
|
|
|
SmallString<128> FileName;
|
|
|
|
if ((EC = sys::fs::createTemporaryFile(Prefix, Suffix, FileName)))
|
|
|
|
fatalError("Unable to create temp file: " + EC.message());
|
|
|
|
return static_cast<std::string>(FileName);
|
|
|
|
}
|
|
|
|
|
|
|
|
ErrorOr<std::string> findClang(const char *Argv0) {
|
|
|
|
StringRef Parent = llvm::sys::path::parent_path(Argv0);
|
|
|
|
ErrorOr<std::string> Path = std::error_code();
|
|
|
|
if (!Parent.empty()) {
|
|
|
|
// First look for the tool with all potential names in the specific
|
|
|
|
// directory of Argv0, if known
|
|
|
|
for (const auto *Name : {"clang", "clang-cl"}) {
|
|
|
|
Path = sys::findProgramByName(Name, Parent);
|
|
|
|
if (Path)
|
|
|
|
return Path;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// If no parent directory known, or not found there, look everywhere in PATH
|
|
|
|
for (const auto *Name : {"clang", "clang-cl"}) {
|
|
|
|
Path = sys::findProgramByName(Name);
|
|
|
|
if (Path)
|
|
|
|
return Path;
|
|
|
|
}
|
|
|
|
return Path;
|
|
|
|
}
|
|
|
|
|
2021-06-18 21:59:58 +02:00
|
|
|
bool isUsableArch(Triple::ArchType Arch) {
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
switch (Arch) {
|
2021-04-21 11:40:39 +02:00
|
|
|
case Triple::x86:
|
|
|
|
case Triple::x86_64:
|
|
|
|
case Triple::arm:
|
|
|
|
case Triple::thumb:
|
|
|
|
case Triple::aarch64:
|
|
|
|
// These work properly with the clang driver, setting the expected
|
|
|
|
// defines such as _WIN32 etc.
|
2021-06-18 21:59:58 +02:00
|
|
|
return true;
|
2021-04-21 11:40:39 +02:00
|
|
|
default:
|
|
|
|
// Other archs aren't set up for use with windows as target OS, (clang
|
2021-06-18 21:59:58 +02:00
|
|
|
// doesn't define e.g. _WIN32 etc), so with them we need to set a
|
|
|
|
// different default arch.
|
|
|
|
return false;
|
2021-04-21 11:40:39 +02:00
|
|
|
}
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
}
|
|
|
|
|
2021-06-18 21:59:58 +02:00
|
|
|
Triple::ArchType getDefaultFallbackArch() {
|
|
|
|
return Triple::x86_64;
|
|
|
|
}
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
std::string getClangClTriple() {
|
|
|
|
Triple T(sys::getDefaultTargetTriple());
|
2021-06-18 21:59:58 +02:00
|
|
|
if (!isUsableArch(T.getArch()))
|
|
|
|
T.setArch(getDefaultFallbackArch());
|
2021-04-21 11:40:39 +02:00
|
|
|
T.setOS(Triple::Win32);
|
|
|
|
T.setVendor(Triple::PC);
|
|
|
|
T.setEnvironment(Triple::MSVC);
|
|
|
|
T.setObjectFormat(Triple::COFF);
|
2021-04-14 15:24:30 +02:00
|
|
|
return T.str();
|
|
|
|
}
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
std::string getMingwTriple() {
|
|
|
|
Triple T(sys::getDefaultTargetTriple());
|
2021-06-18 21:59:58 +02:00
|
|
|
if (!isUsableArch(T.getArch()))
|
|
|
|
T.setArch(getDefaultFallbackArch());
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (T.isWindowsGNUEnvironment())
|
|
|
|
return T.str();
|
|
|
|
// Write out the literal form of the vendor/env here, instead of
|
|
|
|
// constructing them with enum values (which end up with them in
|
|
|
|
// normalized form). The literal form of the triple can matter for
|
|
|
|
// finding include files.
|
|
|
|
return (Twine(T.getArchName()) + "-w64-mingw32").str();
|
|
|
|
}
|
|
|
|
|
|
|
|
enum Format { Rc, Res, Coff, Unknown };
|
|
|
|
|
|
|
|
struct RcOptions {
|
|
|
|
bool Preprocess = true;
|
|
|
|
bool PrintCmdAndExit = false;
|
|
|
|
std::string Triple;
|
|
|
|
std::vector<std::string> PreprocessCmd;
|
|
|
|
std::vector<std::string> PreprocessArgs;
|
|
|
|
|
|
|
|
std::string InputFile;
|
|
|
|
Format InputFormat = Rc;
|
|
|
|
std::string OutputFile;
|
|
|
|
Format OutputFormat = Res;
|
|
|
|
|
|
|
|
bool BeVerbose = false;
|
|
|
|
WriterParams Params;
|
|
|
|
bool AppendNull = false;
|
|
|
|
bool IsDryRun = false;
|
|
|
|
// Set the default language; choose en-US arbitrarily.
|
|
|
|
unsigned LangId = (/*PrimaryLangId*/ 0x09) | (/*SubLangId*/ 0x01 << 10);
|
|
|
|
};
|
|
|
|
|
|
|
|
bool preprocess(StringRef Src, StringRef Dst, const RcOptions &Opts,
|
2021-04-14 15:24:30 +02:00
|
|
|
const char *Argv0) {
|
|
|
|
std::string Clang;
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (Opts.PrintCmdAndExit) {
|
2021-04-14 15:24:30 +02:00
|
|
|
Clang = "clang";
|
|
|
|
} else {
|
|
|
|
ErrorOr<std::string> ClangOrErr = findClang(Argv0);
|
|
|
|
if (ClangOrErr) {
|
|
|
|
Clang = *ClangOrErr;
|
|
|
|
} else {
|
|
|
|
errs() << "llvm-rc: Unable to find clang, skipping preprocessing."
|
|
|
|
<< "\n";
|
|
|
|
errs() << "Pass -no-cpp to disable preprocessing. This will be an error "
|
|
|
|
"in the future."
|
|
|
|
<< "\n";
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
SmallVector<StringRef, 8> Args = {
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Clang, "--driver-mode=gcc", "-target", Opts.Triple, "-E",
|
|
|
|
"-xc", "-DRC_INVOKED"};
|
|
|
|
if (!Opts.PreprocessCmd.empty()) {
|
|
|
|
Args.clear();
|
|
|
|
for (const auto &S : Opts.PreprocessCmd)
|
|
|
|
Args.push_back(S);
|
2021-04-14 15:24:30 +02:00
|
|
|
}
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Args.push_back(Src);
|
|
|
|
Args.push_back("-o");
|
|
|
|
Args.push_back(Dst);
|
|
|
|
for (const auto &S : Opts.PreprocessArgs)
|
|
|
|
Args.push_back(S);
|
|
|
|
if (Opts.PrintCmdAndExit || Opts.BeVerbose) {
|
2021-04-14 15:24:30 +02:00
|
|
|
for (const auto &A : Args) {
|
|
|
|
outs() << " ";
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
sys::printArg(outs(), A, Opts.PrintCmdAndExit);
|
2021-04-14 15:24:30 +02:00
|
|
|
}
|
|
|
|
outs() << "\n";
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (Opts.PrintCmdAndExit)
|
2021-04-14 15:24:30 +02:00
|
|
|
exit(0);
|
|
|
|
}
|
|
|
|
// The llvm Support classes don't handle reading from stdout of a child
|
|
|
|
// process; otherwise we could avoid using a temp file.
|
|
|
|
int Res = sys::ExecuteAndWait(Clang, Args);
|
|
|
|
if (Res) {
|
|
|
|
fatalError("llvm-rc: Preprocessing failed.");
|
|
|
|
}
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
static std::pair<bool, std::string> isWindres(llvm::StringRef Argv0) {
|
|
|
|
StringRef ProgName = llvm::sys::path::stem(Argv0);
|
|
|
|
// x86_64-w64-mingw32-windres -> x86_64-w64-mingw32, windres
|
|
|
|
// llvm-rc -> "", llvm-rc
|
|
|
|
// aarch64-w64-mingw32-llvm-windres-10.exe -> aarch64-w64-mingw32, llvm-windres
|
|
|
|
ProgName = ProgName.rtrim("0123456789.-");
|
2021-06-23 13:52:36 +02:00
|
|
|
if (!ProgName.consume_back_insensitive("windres"))
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
return std::make_pair<bool, std::string>(false, "");
|
2021-06-23 13:52:36 +02:00
|
|
|
ProgName.consume_back_insensitive("llvm-");
|
|
|
|
ProgName.consume_back_insensitive("-");
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
return std::make_pair<bool, std::string>(true, ProgName.str());
|
|
|
|
}
|
2017-07-25 02:25:18 +02:00
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Format parseFormat(StringRef S) {
|
|
|
|
Format F = StringSwitch<Format>(S.lower())
|
|
|
|
.Case("rc", Rc)
|
|
|
|
.Case("res", Res)
|
|
|
|
.Case("coff", Coff)
|
|
|
|
.Default(Unknown);
|
|
|
|
if (F == Unknown)
|
|
|
|
fatalError("Unable to parse '" + Twine(S) + "' as a format");
|
|
|
|
return F;
|
|
|
|
}
|
|
|
|
|
|
|
|
void deduceFormat(Format &Dest, StringRef File) {
|
|
|
|
Format F = StringSwitch<Format>(sys::path::extension(File.lower()))
|
|
|
|
.Case(".rc", Rc)
|
|
|
|
.Case(".res", Res)
|
|
|
|
.Case(".o", Coff)
|
|
|
|
.Case(".obj", Coff)
|
|
|
|
.Default(Unknown);
|
|
|
|
if (F != Unknown)
|
|
|
|
Dest = F;
|
|
|
|
}
|
|
|
|
|
|
|
|
std::string unescape(StringRef S) {
|
|
|
|
std::string Out;
|
|
|
|
Out.reserve(S.size());
|
|
|
|
for (int I = 0, E = S.size(); I < E; I++) {
|
|
|
|
if (S[I] == '\\') {
|
|
|
|
if (I + 1 < E)
|
|
|
|
Out.push_back(S[++I]);
|
|
|
|
else
|
|
|
|
fatalError("Unterminated escape");
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
Out.push_back(S[I]);
|
|
|
|
}
|
|
|
|
return Out;
|
|
|
|
}
|
|
|
|
|
|
|
|
std::vector<std::string> unescapeSplit(StringRef S) {
|
|
|
|
std::vector<std::string> OutArgs;
|
|
|
|
std::string Out;
|
|
|
|
bool InQuote = false;
|
|
|
|
for (int I = 0, E = S.size(); I < E; I++) {
|
|
|
|
if (S[I] == '\\') {
|
|
|
|
if (I + 1 < E)
|
|
|
|
Out.push_back(S[++I]);
|
|
|
|
else
|
|
|
|
fatalError("Unterminated escape");
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
if (S[I] == '"') {
|
|
|
|
InQuote = !InQuote;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
if (S[I] == ' ' && !InQuote) {
|
|
|
|
OutArgs.push_back(Out);
|
|
|
|
Out.clear();
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
Out.push_back(S[I]);
|
|
|
|
}
|
|
|
|
if (InQuote)
|
|
|
|
fatalError("Unterminated quote");
|
|
|
|
if (!Out.empty())
|
|
|
|
OutArgs.push_back(Out);
|
|
|
|
return OutArgs;
|
|
|
|
}
|
|
|
|
|
|
|
|
RcOptions parseWindresOptions(ArrayRef<const char *> ArgsArr,
|
|
|
|
ArrayRef<const char *> InputArgsArray,
|
|
|
|
std::string Prefix) {
|
|
|
|
WindresOptTable T;
|
|
|
|
RcOptions Opts;
|
2017-07-25 02:25:18 +02:00
|
|
|
unsigned MAI, MAC;
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
opt::InputArgList InputArgs = T.ParseArgs(ArgsArr, MAI, MAC);
|
|
|
|
|
|
|
|
// The tool prints nothing when invoked with no command-line arguments.
|
|
|
|
if (InputArgs.hasArg(WINDRES_help)) {
|
2021-06-24 23:47:03 +02:00
|
|
|
T.printHelp(outs(), "windres [options] file...",
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
"LLVM windres (GNU windres compatible)", false, true);
|
|
|
|
exit(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (InputArgs.hasArg(WINDRES_version)) {
|
|
|
|
outs() << "llvm-windres, compatible with GNU windres\n";
|
|
|
|
cl::PrintVersionMessage();
|
|
|
|
exit(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
std::vector<std::string> FileArgs = InputArgs.getAllArgValues(WINDRES_INPUT);
|
|
|
|
FileArgs.insert(FileArgs.end(), InputArgsArray.begin(), InputArgsArray.end());
|
|
|
|
|
|
|
|
if (InputArgs.hasArg(WINDRES_input)) {
|
|
|
|
Opts.InputFile = InputArgs.getLastArgValue(WINDRES_input).str();
|
|
|
|
} else if (!FileArgs.empty()) {
|
|
|
|
Opts.InputFile = FileArgs.front();
|
|
|
|
FileArgs.erase(FileArgs.begin());
|
|
|
|
} else {
|
|
|
|
// TODO: GNU windres takes input on stdin in this case.
|
|
|
|
fatalError("Missing input file");
|
|
|
|
}
|
|
|
|
|
|
|
|
if (InputArgs.hasArg(WINDRES_output)) {
|
|
|
|
Opts.OutputFile = InputArgs.getLastArgValue(WINDRES_output).str();
|
|
|
|
} else if (!FileArgs.empty()) {
|
|
|
|
Opts.OutputFile = FileArgs.front();
|
|
|
|
FileArgs.erase(FileArgs.begin());
|
|
|
|
} else {
|
|
|
|
// TODO: GNU windres writes output in rc form to stdout in this case.
|
|
|
|
fatalError("Missing output file");
|
|
|
|
}
|
|
|
|
|
|
|
|
if (InputArgs.hasArg(WINDRES_input_format)) {
|
|
|
|
Opts.InputFormat =
|
|
|
|
parseFormat(InputArgs.getLastArgValue(WINDRES_input_format));
|
|
|
|
} else {
|
|
|
|
deduceFormat(Opts.InputFormat, Opts.InputFile);
|
|
|
|
}
|
|
|
|
if (Opts.InputFormat == Coff)
|
|
|
|
fatalError("Unsupported input format");
|
|
|
|
|
|
|
|
if (InputArgs.hasArg(WINDRES_output_format)) {
|
|
|
|
Opts.OutputFormat =
|
|
|
|
parseFormat(InputArgs.getLastArgValue(WINDRES_output_format));
|
|
|
|
} else {
|
|
|
|
// The default in windres differs from the default in RcOptions
|
|
|
|
Opts.OutputFormat = Coff;
|
|
|
|
deduceFormat(Opts.OutputFormat, Opts.OutputFile);
|
|
|
|
}
|
|
|
|
if (Opts.OutputFormat == Rc)
|
|
|
|
fatalError("Unsupported output format");
|
|
|
|
if (Opts.InputFormat == Opts.OutputFormat) {
|
|
|
|
outs() << "Nothing to do.\n";
|
|
|
|
exit(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
Opts.PrintCmdAndExit = InputArgs.hasArg(WINDRES__HASH_HASH_HASH);
|
|
|
|
Opts.Preprocess = !InputArgs.hasArg(WINDRES_no_preprocess);
|
|
|
|
Triple TT(Prefix);
|
|
|
|
if (InputArgs.hasArg(WINDRES_target)) {
|
|
|
|
StringRef Value = InputArgs.getLastArgValue(WINDRES_target);
|
|
|
|
if (Value == "pe-i386")
|
|
|
|
Opts.Triple = "i686-w64-mingw32";
|
|
|
|
else if (Value == "pe-x86-64")
|
|
|
|
Opts.Triple = "x86_64-w64-mingw32";
|
|
|
|
else
|
|
|
|
// Implicit extension; if the --target value isn't one of the known
|
|
|
|
// BFD targets, allow setting the full triple string via this instead.
|
|
|
|
Opts.Triple = Value.str();
|
|
|
|
} else if (TT.getArch() != Triple::UnknownArch)
|
|
|
|
Opts.Triple = Prefix;
|
|
|
|
else
|
|
|
|
Opts.Triple = getMingwTriple();
|
2019-01-16 09:09:22 +01:00
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
for (const auto *Arg :
|
|
|
|
InputArgs.filtered(WINDRES_include_dir, WINDRES_define, WINDRES_undef,
|
|
|
|
WINDRES_preprocessor_arg)) {
|
|
|
|
// GNU windres passes the arguments almost as-is on to popen() (it only
|
|
|
|
// backslash escapes spaces in the arguments), where a shell would
|
|
|
|
// unescape backslash escapes for quotes and similar. This means that
|
|
|
|
// when calling GNU windres, callers need to double escape chars like
|
|
|
|
// quotes, e.g. as -DSTRING=\\\"1.2.3\\\".
|
|
|
|
//
|
|
|
|
// Exactly how the arguments are interpreted depends on the platform
|
|
|
|
// though - but the cases where this matters (where callers would have
|
|
|
|
// done this double escaping) probably is confined to cases like these
|
|
|
|
// quoted string defines, and those happen to work the same across unix
|
|
|
|
// and windows.
|
|
|
|
std::string Unescaped = unescape(Arg->getValue());
|
|
|
|
switch (Arg->getOption().getID()) {
|
|
|
|
case WINDRES_include_dir:
|
|
|
|
// Technically, these are handled the same way as e.g. defines, but
|
|
|
|
// the way we consistently unescape the unix way breaks windows paths
|
|
|
|
// with single backslashes. Alternatively, our unescape function would
|
|
|
|
// need to mimic the platform specific command line parsing/unescaping
|
|
|
|
// logic.
|
|
|
|
Opts.Params.Include.push_back(Arg->getValue());
|
|
|
|
Opts.PreprocessArgs.push_back("-I");
|
|
|
|
Opts.PreprocessArgs.push_back(Arg->getValue());
|
|
|
|
break;
|
|
|
|
case WINDRES_define:
|
|
|
|
Opts.PreprocessArgs.push_back("-D");
|
|
|
|
Opts.PreprocessArgs.push_back(Unescaped);
|
|
|
|
break;
|
|
|
|
case WINDRES_undef:
|
|
|
|
Opts.PreprocessArgs.push_back("-U");
|
|
|
|
Opts.PreprocessArgs.push_back(Unescaped);
|
|
|
|
break;
|
|
|
|
case WINDRES_preprocessor_arg:
|
|
|
|
Opts.PreprocessArgs.push_back(Unescaped);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (InputArgs.hasArg(WINDRES_preprocessor))
|
|
|
|
Opts.PreprocessCmd =
|
|
|
|
unescapeSplit(InputArgs.getLastArgValue(WINDRES_preprocessor));
|
|
|
|
|
|
|
|
Opts.Params.CodePage = CpWin1252; // Different default
|
|
|
|
if (InputArgs.hasArg(WINDRES_codepage)) {
|
|
|
|
if (InputArgs.getLastArgValue(WINDRES_codepage)
|
|
|
|
.getAsInteger(10, Opts.Params.CodePage))
|
|
|
|
fatalError("Invalid code page: " +
|
|
|
|
InputArgs.getLastArgValue(WINDRES_codepage));
|
|
|
|
}
|
|
|
|
if (InputArgs.hasArg(WINDRES_language)) {
|
|
|
|
if (InputArgs.getLastArgValue(WINDRES_language)
|
|
|
|
.getAsInteger(16, Opts.LangId))
|
|
|
|
fatalError("Invalid language id: " +
|
|
|
|
InputArgs.getLastArgValue(WINDRES_language));
|
|
|
|
}
|
|
|
|
|
|
|
|
Opts.BeVerbose = InputArgs.hasArg(WINDRES_verbose);
|
|
|
|
|
|
|
|
return Opts;
|
|
|
|
}
|
|
|
|
|
|
|
|
RcOptions parseRcOptions(ArrayRef<const char *> ArgsArr,
|
|
|
|
ArrayRef<const char *> InputArgsArray) {
|
|
|
|
RcOptTable T;
|
|
|
|
RcOptions Opts;
|
|
|
|
unsigned MAI, MAC;
|
2017-07-25 02:25:18 +02:00
|
|
|
opt::InputArgList InputArgs = T.ParseArgs(ArgsArr, MAI, MAC);
|
|
|
|
|
|
|
|
// The tool prints nothing when invoked with no command-line arguments.
|
2020-08-05 10:00:21 +02:00
|
|
|
if (InputArgs.hasArg(OPT_help)) {
|
2021-06-24 23:47:03 +02:00
|
|
|
T.printHelp(outs(), "rc [options] file...", "Resource Converter", false);
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
exit(0);
|
2017-08-10 18:21:44 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
std::vector<std::string> InArgsInfo = InputArgs.getAllArgValues(OPT_INPUT);
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
InArgsInfo.insert(InArgsInfo.end(), InputArgsArray.begin(),
|
|
|
|
InputArgsArray.end());
|
2017-08-10 18:21:44 +02:00
|
|
|
if (InArgsInfo.size() != 1) {
|
|
|
|
fatalError("Exactly one input file should be provided.");
|
|
|
|
}
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Opts.PrintCmdAndExit = InputArgs.hasArg(OPT__HASH_HASH_HASH);
|
|
|
|
Opts.Triple = getClangClTriple();
|
|
|
|
for (const auto *Arg :
|
|
|
|
InputArgs.filtered(OPT_includepath, OPT_define, OPT_undef)) {
|
|
|
|
switch (Arg->getOption().getID()) {
|
|
|
|
case OPT_includepath:
|
|
|
|
Opts.PreprocessArgs.push_back("-I");
|
|
|
|
break;
|
|
|
|
case OPT_define:
|
|
|
|
Opts.PreprocessArgs.push_back("-D");
|
|
|
|
break;
|
|
|
|
case OPT_undef:
|
|
|
|
Opts.PreprocessArgs.push_back("-U");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
Opts.PreprocessArgs.push_back(Arg->getValue());
|
|
|
|
}
|
|
|
|
|
|
|
|
Opts.InputFile = InArgsInfo[0];
|
|
|
|
Opts.BeVerbose = InputArgs.hasArg(OPT_verbose);
|
|
|
|
Opts.Preprocess = !InputArgs.hasArg(OPT_no_preprocess);
|
|
|
|
Opts.Params.Include = InputArgs.getAllArgValues(OPT_includepath);
|
|
|
|
Opts.Params.NoInclude = InputArgs.hasArg(OPT_noinclude);
|
|
|
|
if (Opts.Params.NoInclude) {
|
|
|
|
// Clear the INLCUDE variable for the external preprocessor
|
|
|
|
#ifdef _WIN32
|
|
|
|
::_putenv("INCLUDE=");
|
|
|
|
#else
|
|
|
|
::unsetenv("INCLUDE");
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
if (InputArgs.hasArg(OPT_codepage)) {
|
|
|
|
if (InputArgs.getLastArgValue(OPT_codepage)
|
|
|
|
.getAsInteger(10, Opts.Params.CodePage))
|
|
|
|
fatalError("Invalid code page: " +
|
|
|
|
InputArgs.getLastArgValue(OPT_codepage));
|
|
|
|
}
|
|
|
|
Opts.IsDryRun = InputArgs.hasArg(OPT_dry_run);
|
|
|
|
auto OutArgsInfo = InputArgs.getAllArgValues(OPT_fileout);
|
|
|
|
if (OutArgsInfo.empty()) {
|
|
|
|
SmallString<128> OutputFile(Opts.InputFile);
|
|
|
|
llvm::sys::fs::make_absolute(OutputFile);
|
|
|
|
llvm::sys::path::replace_extension(OutputFile, "res");
|
|
|
|
OutArgsInfo.push_back(std::string(OutputFile.str()));
|
|
|
|
}
|
|
|
|
if (!Opts.IsDryRun) {
|
|
|
|
if (OutArgsInfo.size() != 1)
|
|
|
|
fatalError(
|
|
|
|
"No more than one output file should be provided (using /FO flag).");
|
|
|
|
Opts.OutputFile = OutArgsInfo[0];
|
|
|
|
}
|
|
|
|
Opts.AppendNull = InputArgs.hasArg(OPT_add_null);
|
|
|
|
if (InputArgs.hasArg(OPT_lang_id)) {
|
|
|
|
if (InputArgs.getLastArgValue(OPT_lang_id).getAsInteger(16, Opts.LangId))
|
|
|
|
fatalError("Invalid language id: " +
|
|
|
|
InputArgs.getLastArgValue(OPT_lang_id));
|
|
|
|
}
|
|
|
|
return Opts;
|
|
|
|
}
|
|
|
|
|
|
|
|
RcOptions getOptions(const char *Argv0, ArrayRef<const char *> ArgsArr,
|
|
|
|
ArrayRef<const char *> InputArgs) {
|
|
|
|
std::string Prefix;
|
|
|
|
bool IsWindres;
|
|
|
|
std::tie(IsWindres, Prefix) = isWindres(Argv0);
|
|
|
|
if (IsWindres)
|
|
|
|
return parseWindresOptions(ArgsArr, InputArgs, Prefix);
|
|
|
|
else
|
|
|
|
return parseRcOptions(ArgsArr, InputArgs);
|
|
|
|
}
|
|
|
|
|
|
|
|
void doRc(std::string Src, std::string Dest, RcOptions &Opts,
|
|
|
|
const char *Argv0) {
|
|
|
|
std::string PreprocessedFile = Src;
|
|
|
|
if (Opts.Preprocess) {
|
2021-04-14 15:24:30 +02:00
|
|
|
std::string OutFile = createTempFile("preproc", "rc");
|
|
|
|
TempPreprocFile.setFile(OutFile);
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (preprocess(Src, OutFile, Opts, Argv0))
|
2021-04-14 15:24:30 +02:00
|
|
|
PreprocessedFile = OutFile;
|
|
|
|
}
|
|
|
|
|
2017-08-10 18:21:44 +02:00
|
|
|
// Read and tokenize the input file.
|
2017-10-11 22:12:09 +02:00
|
|
|
ErrorOr<std::unique_ptr<MemoryBuffer>> File =
|
2021-04-14 15:24:30 +02:00
|
|
|
MemoryBuffer::getFile(PreprocessedFile);
|
2017-08-10 18:21:44 +02:00
|
|
|
if (!File) {
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
fatalError("Error opening file '" + Twine(PreprocessedFile) +
|
2017-08-10 18:21:44 +02:00
|
|
|
"': " + File.getError().message());
|
|
|
|
}
|
|
|
|
|
|
|
|
std::unique_ptr<MemoryBuffer> FileContents = std::move(*File);
|
|
|
|
StringRef Contents = FileContents->getBuffer();
|
|
|
|
|
2018-05-09 20:21:03 +02:00
|
|
|
std::string FilteredContents = filterCppOutput(Contents);
|
|
|
|
std::vector<RCToken> Tokens = ExitOnErr(tokenizeRC(FilteredContents));
|
2017-08-10 18:21:44 +02:00
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (Opts.BeVerbose) {
|
2017-08-10 18:21:44 +02:00
|
|
|
const Twine TokenNames[] = {
|
|
|
|
#define TOKEN(Name) #Name,
|
|
|
|
#define SHORT_TOKEN(Name, Ch) #Name,
|
2017-11-21 01:23:19 +01:00
|
|
|
#include "ResourceScriptTokenList.def"
|
2017-08-10 18:21:44 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
for (const RCToken &Token : Tokens) {
|
|
|
|
outs() << TokenNames[static_cast<int>(Token.kind())] << ": "
|
|
|
|
<< Token.value();
|
|
|
|
if (Token.kind() == RCToken::Kind::Int)
|
|
|
|
outs() << "; int value = " << Token.intValue();
|
|
|
|
|
|
|
|
outs() << "\n";
|
|
|
|
}
|
|
|
|
}
|
2017-07-25 02:25:18 +02:00
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
WriterParams &Params = Opts.Params;
|
|
|
|
SmallString<128> InputFile(Src);
|
2017-10-11 22:12:09 +02:00
|
|
|
llvm::sys::fs::make_absolute(InputFile);
|
|
|
|
Params.InputFilePath = InputFile;
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
switch (Params.CodePage) {
|
|
|
|
case CpAcp:
|
|
|
|
case CpWin1252:
|
|
|
|
case CpUtf8:
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
fatalError("Unsupported code page, only 0, 1252 and 65001 are supported!");
|
2018-05-02 21:43:44 +02:00
|
|
|
}
|
|
|
|
|
2017-09-29 19:14:09 +02:00
|
|
|
std::unique_ptr<ResourceFileWriter> Visitor;
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (!Opts.IsDryRun) {
|
2017-09-29 19:14:09 +02:00
|
|
|
std::error_code EC;
|
2019-08-15 17:54:37 +02:00
|
|
|
auto FOut = std::make_unique<raw_fd_ostream>(
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Dest, EC, sys::fs::FA_Read | sys::fs::FA_Write);
|
2017-09-29 19:14:09 +02:00
|
|
|
if (EC)
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
fatalError("Error opening output file '" + Dest + "': " + EC.message());
|
2019-08-15 17:54:37 +02:00
|
|
|
Visitor = std::make_unique<ResourceFileWriter>(Params, std::move(FOut));
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
Visitor->AppendNull = Opts.AppendNull;
|
2017-09-29 19:14:09 +02:00
|
|
|
|
|
|
|
ExitOnErr(NullResource().visit(Visitor.get()));
|
|
|
|
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
unsigned PrimaryLangId = Opts.LangId & 0x3ff;
|
|
|
|
unsigned SubLangId = Opts.LangId >> 10;
|
2020-06-20 22:34:53 +02:00
|
|
|
ExitOnErr(LanguageResource(PrimaryLangId, SubLangId).visit(Visitor.get()));
|
2017-09-29 19:14:09 +02:00
|
|
|
}
|
|
|
|
|
2017-08-18 20:24:17 +02:00
|
|
|
rc::RCParser Parser{std::move(Tokens)};
|
|
|
|
while (!Parser.isEof()) {
|
|
|
|
auto Resource = ExitOnErr(Parser.parseSingleResource());
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (Opts.BeVerbose)
|
2017-08-18 20:24:17 +02:00
|
|
|
Resource->log(outs());
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (!Opts.IsDryRun)
|
2017-09-29 19:14:09 +02:00
|
|
|
ExitOnErr(Resource->visit(Visitor.get()));
|
2017-08-18 20:24:17 +02:00
|
|
|
}
|
|
|
|
|
2017-10-06 23:30:55 +02:00
|
|
|
// STRINGTABLE resources come at the very end.
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
if (!Opts.IsDryRun)
|
2017-10-06 23:30:55 +02:00
|
|
|
ExitOnErr(Visitor->dumpAllStringTables());
|
[llvm-rc] Add a GNU windres-like frontend to llvm-rc
This primarily parses a different set of options and invokes the same
resource compiler as llvm-rc normally. Additionally, it can convert
directly to an object file (which in MSVC style setups is done with the
separate cvtres tool, or by the linker).
(GNU windres also supports other conversions; from coff object file back
to .res, and from .res or object file back to .rc form; that's not yet
implemented.)
The other bigger complication lies in being able to imply or pass the
intended target triple, to let clang find the corresponding mingw sysroot
for finding include files, and for specifying the default output object
machine format.
It can be implied from the tool triple prefix, like
`<triple>-[llvm-]windres` or picked up from the windres option e.g.
`-F pe-x86-64`. In GNU windres, that option takes BFD style format names
such as pe-i386 or pe-x86-64. As libbfd in binutils doesn't support
Windows on ARM, there's no such canonical name for the ARM targets.
Therefore, as an LLVM specific extension, this option is extended to
allow passing full triples, too.
Differential Revision: https://reviews.llvm.org/D100756
2021-04-15 13:38:27 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void doCvtres(std::string Src, std::string Dest, std::string TargetTriple) {
|
|
|
|
object::WindowsResourceParser Parser;
|
|
|
|
|
|
|
|
ErrorOr<std::unique_ptr<MemoryBuffer>> BufferOrErr =
|
|
|
|
MemoryBuffer::getFile(Src);
|
|
|
|
if (!BufferOrErr)
|
|
|
|
fatalError("Error opening file '" + Twine(Src) +
|
|
|
|
"': " + BufferOrErr.getError().message());
|
|
|
|
std::unique_ptr<MemoryBuffer> &Buffer = BufferOrErr.get();
|
|
|
|
std::unique_ptr<object::WindowsResource> Binary =
|
|
|
|
ExitOnErr(object::WindowsResource::createWindowsResource(
|
|
|
|
Buffer->getMemBufferRef()));
|
|
|
|
|
|
|
|
std::vector<std::string> Duplicates;
|
|
|
|
ExitOnErr(Parser.parse(Binary.get(), Duplicates));
|
|
|
|
for (const auto &DupeDiag : Duplicates)
|
|
|
|
fatalError("Duplicate resources: " + DupeDiag);
|
|
|
|
|
|
|
|
Triple T(TargetTriple);
|
|
|
|
COFF::MachineTypes MachineType;
|
|
|
|
switch (T.getArch()) {
|
|
|
|
case Triple::x86:
|
|
|
|
MachineType = COFF::IMAGE_FILE_MACHINE_I386;
|
|
|
|
break;
|
|
|
|
case Triple::x86_64:
|
|
|
|
MachineType = COFF::IMAGE_FILE_MACHINE_AMD64;
|
|
|
|
break;
|
|
|
|
case Triple::arm:
|
|
|
|
case Triple::thumb:
|
|
|
|
MachineType = COFF::IMAGE_FILE_MACHINE_ARMNT;
|
|
|
|
break;
|
|
|
|
case Triple::aarch64:
|
|
|
|
MachineType = COFF::IMAGE_FILE_MACHINE_ARM64;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
fatalError("Unsupported architecture in target '" + Twine(TargetTriple) +
|
|
|
|
"'");
|
|
|
|
}
|
|
|
|
|
|
|
|
std::unique_ptr<MemoryBuffer> OutputBuffer =
|
|
|
|
ExitOnErr(object::writeWindowsResourceCOFF(MachineType, Parser,
|
|
|
|
/*DateTimeStamp*/ 0));
|
|
|
|
std::unique_ptr<FileOutputBuffer> FileBuffer =
|
|
|
|
ExitOnErr(FileOutputBuffer::create(Dest, OutputBuffer->getBufferSize()));
|
|
|
|
std::copy(OutputBuffer->getBufferStart(), OutputBuffer->getBufferEnd(),
|
|
|
|
FileBuffer->getBufferStart());
|
|
|
|
ExitOnErr(FileBuffer->commit());
|
|
|
|
}
|
|
|
|
|
|
|
|
} // anonymous namespace
|
|
|
|
|
|
|
|
int main(int Argc, const char **Argv) {
|
|
|
|
InitLLVM X(Argc, Argv);
|
|
|
|
ExitOnErr.setBanner("llvm-rc: ");
|
|
|
|
|
|
|
|
const char **DashDash = std::find_if(
|
|
|
|
Argv + 1, Argv + Argc, [](StringRef Str) { return Str == "--"; });
|
|
|
|
ArrayRef<const char *> ArgsArr = makeArrayRef(Argv + 1, DashDash);
|
|
|
|
ArrayRef<const char *> FileArgsArr;
|
|
|
|
if (DashDash != Argv + Argc)
|
|
|
|
FileArgsArr = makeArrayRef(DashDash + 1, Argv + Argc);
|
|
|
|
|
|
|
|
RcOptions Opts = getOptions(Argv[0], ArgsArr, FileArgsArr);
|
|
|
|
|
|
|
|
std::string ResFile = Opts.OutputFile;
|
|
|
|
if (Opts.InputFormat == Rc) {
|
|
|
|
if (Opts.OutputFormat == Coff) {
|
|
|
|
ResFile = createTempFile("rc", "res");
|
|
|
|
TempResFile.setFile(ResFile);
|
|
|
|
}
|
|
|
|
doRc(Opts.InputFile, ResFile, Opts, Argv[0]);
|
|
|
|
} else {
|
|
|
|
ResFile = Opts.InputFile;
|
|
|
|
}
|
|
|
|
if (Opts.OutputFormat == Coff) {
|
|
|
|
doCvtres(ResFile, Opts.OutputFile, Opts.Triple);
|
|
|
|
}
|
2017-10-06 23:30:55 +02:00
|
|
|
|
2017-07-25 02:25:18 +02:00
|
|
|
return 0;
|
|
|
|
}
|