有哪些聪明的解决方案可以将资源包含在静态库中？

发布于 2024-11-27 20:32:40 字数 550 浏览 1 评论 0原文

我有一个静态库 Xcode 4 项目，其中包含一个自制的渲染引擎，并且我在多个应用程序中重复使用该引擎。该引擎使用 OpenGL ES 2.0 以及扩展的着色器。随着着色器变得更加复杂，我不再将它们存储为源文件中的 NSString，现在将它们存储为带有 .vert 和 .frag 扩展名的独立文本文件。

这对于在自己的源代码中包含渲染引擎的应用程序来说效果很好；着色器只是添加到应用程序的“复制捆绑资源”构建阶段，并在运行时加载到 NSStrings 中并进行编译、链接等。

如果加载这些着色器的渲染引擎位于静态库中，则此策略根本不起作用项目;没有可以复制资源的包。目前，我被迫让静态库渲染引擎的每个客户端项目在自己的“复制捆绑资源”构建阶段包含自己的着色器副本。这是一个巨大的痛苦，并且首先破坏了将渲染引擎变成静态库的大部分便利性。

我想这是“静态库中的资源”这个更普遍的问题的具体实例。我能想到的最佳解决方案是将着色器文件的内容复制到头文件中的字符串中，然后将其包含在渲染引擎的源代码中。我什至可以使用一些“运行脚本”构建阶段魔法自动从 .frag 到 .h 的转换，但不幸的是它看起来很复杂。

我有什么遗漏的吗？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

惯饮孤独 2024-12-04 20:32:41

为了后代的利益，我将分享我最终使用的解决方案。从较高层面来看，解决方案是将相关资源编译到应用程序二进制文件中，从而避免将其复制到捆绑资源中的需要。

我决定将任何文件数据编译为二进制文件的通用且可靠的方法是将文件内容存储在头文件中的静态字节数组中。假设已经创建了一个头文件并将其添加到静态 lib 目标中，我制作了以下 bash 脚本来读取文件，并使用 C 语法将其内容写入十六进制文字的字节数组。然后，我在编译源和复制头构建阶段之前的“运行脚本”构建阶段中运行脚本：

#!/bin/bash
# Hexify.sh reads an input file, and hexdumps its contents to an output
# file in C-compliant syntax. The final argument is the name of the array.

infile=$1
outfile=$2
arrayName=$3

fileSize=$(stat -f "%z" $infile)
fileHexString=$(hexdump -ve '1/1 "0x%.2x, "' $infile)

prefix=$arrayName
suffix="Size"
variableName=$arrayName$suffix
nullTermination="0x00"

echo "//" > $headerFile
echo "//  This file was automatically generated by a build script." >> $headerFile
echo "//  Do not modify; the contents of this file will be overwritten on each build." >> $headerFile
echo "//" >> $headerFile
echo "" >> $headerFile;
echo "#ifndef some_arbitrary_include_guard" >> $headerFile
echo "#define some_arbitrary_include_guard" >> $headerFile
echo "" >> $headerFile
echo "static const int $variableName = $((fileSize+1));" >> $outfile
echo "static const char $arrayName[$variableName] = {" >> $outfile
echo -e "\t$fileHexString$nullTermination" >> $outfile
echo "};" >> $outfile
echo "#endif" >> $headerFile

因此，例如，如果我有一个资源文件 example.txt：

Hello this
is a file

我要运行 < code>./Hexify.sh example.txt myHeader.h exampleArray，标题将如下所示：

//
//  This file was automatically generated by a build script.
//  Do not modify; the contents of this file will be overwritten on each build.
//

#ifndef some_arbitrary_include_guard
#define some_arbitrary_include_guard

static const int exampleArraySize = 21;
static const char exampleArray[exampleArraySize] = {
    0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x74, 0x68, 0x69, 0x73, 0x0a,
    0x69, 0x73, 0x20, 0x61, 0x20, 0x66, 0x69, 0x6c, 0x65, 0x00
};
#endif

现在，在我从主包加载所述资源的任何时间点，我可以改为参考该头文件中的字节数组。请注意，我的脚本版本添加了一个空终止字节，这使得数据适合创建字符串对象。这可能并不适用于所有情况。

作为最后的附录，如果 bash 脚本让任何真正的 bash 程序员感到畏缩，我深表歉意；我几乎不知道我在用 bash 做什么。

For the benefit of posterity, I'll share the solution I ended up using. At a high level, the solution is to compile the resource in question into the application binary, thus obviating the need to also copy it to bundle resources.

I decided a generic and reliable way to compile any file data into the binary would be to store the file contents in a static byte array in a header file. Assuming there is already a header file created and added to the static lib target, I made the following bash script to read a file, and write its contents as a byte array of hex literals with C syntax. I then run the script in "Run Script" build phase before the Compile Sources and Copy Headers build phases:

#!/bin/bash
# Hexify.sh reads an input file, and hexdumps its contents to an output
# file in C-compliant syntax. The final argument is the name of the array.

infile=$1
outfile=$2
arrayName=$3

fileSize=$(stat -f "%z" $infile)
fileHexString=$(hexdump -ve '1/1 "0x%.2x, "' $infile)

prefix=$arrayName
suffix="Size"
variableName=$arrayName$suffix
nullTermination="0x00"

echo "//" > $headerFile
echo "//  This file was automatically generated by a build script." >> $headerFile
echo "//  Do not modify; the contents of this file will be overwritten on each build." >> $headerFile
echo "//" >> $headerFile
echo "" >> $headerFile;
echo "#ifndef some_arbitrary_include_guard" >> $headerFile
echo "#define some_arbitrary_include_guard" >> $headerFile
echo "" >> $headerFile
echo "static const int $variableName = $((fileSize+1));" >> $outfile
echo "static const char $arrayName[$variableName] = {" >> $outfile
echo -e "\t$fileHexString$nullTermination" >> $outfile
echo "};" >> $outfile
echo "#endif" >> $headerFile

So, for example, if I have a resource file example.txt:

Hello this
is a file

And I were to run ./Hexify.sh example.txt myHeader.h exampleArray, the header would look like this:

//
//  This file was automatically generated by a build script.
//  Do not modify; the contents of this file will be overwritten on each build.
//

#ifndef some_arbitrary_include_guard
#define some_arbitrary_include_guard

static const int exampleArraySize = 21;
static const char exampleArray[exampleArraySize] = {
    0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x74, 0x68, 0x69, 0x73, 0x0a,
    0x69, 0x73, 0x20, 0x61, 0x20, 0x66, 0x69, 0x6c, 0x65, 0x00
};
#endif

Now, at any point in time that I would have loaded said resource from the main bundle, I can instead refer to the byte array in that header file. Note that my version of the script adds a null terminated byte, which makes the data suitable for creating string objects. That may not apply in all cases.

As one final addendum, I apologize if that bash script makes any real bash programmers cringe; I have almost no idea what I'm doing with bash.

回复收藏 0 原文