Merge branch 'master' into write-async-await
This commit is contained in:
commit
9bfe091024
|
@ -7,4 +7,6 @@ public interface IEssayScanService
|
|||
public Task<BlogContents> ScanContents();
|
||||
|
||||
public Task SaveBlogContent(BlogContent content, bool isDraft = true);
|
||||
|
||||
public Task<ImageScanResult> ScanImages();
|
||||
}
|
||||
|
|
3
YaeBlog.Core/Models/ImageScanResult.cs
Normal file
3
YaeBlog.Core/Models/ImageScanResult.cs
Normal file
|
@ -0,0 +1,3 @@
|
|||
namespace YaeBlog.Core.Models;
|
||||
|
||||
public record struct ImageScanResult(List<FileInfo> UnusedImages, List<FileInfo> NotFoundImages);
|
|
@ -1,4 +1,5 @@
|
|||
using System.Collections.Concurrent;
|
||||
using System.Text.RegularExpressions;
|
||||
using Microsoft.Extensions.Logging;
|
||||
using Microsoft.Extensions.Options;
|
||||
using YaeBlog.Core.Abstractions;
|
||||
|
@ -9,7 +10,7 @@ using YamlDotNet.Serialization;
|
|||
|
||||
namespace YaeBlog.Core.Services;
|
||||
|
||||
public class EssayScanService(
|
||||
public partial class EssayScanService(
|
||||
ISerializer yamlSerializer,
|
||||
IDeserializer yamlDeserializer,
|
||||
IOptions<BlogOptions> blogOptions,
|
||||
|
@ -34,6 +35,11 @@ public class EssayScanService(
|
|||
? new FileInfo(Path.Combine(drafts.FullName, content.FileName + ".md"))
|
||||
: new FileInfo(Path.Combine(posts.FullName, content.FileName + ".md"));
|
||||
|
||||
if (!isDraft)
|
||||
{
|
||||
content.Metadata.Date = DateTime.Now;
|
||||
}
|
||||
|
||||
if (targetFile.Exists)
|
||||
{
|
||||
logger.LogWarning("Blog {} exists, overriding.", targetFile.Name);
|
||||
|
@ -44,7 +50,15 @@ public class EssayScanService(
|
|||
await writer.WriteAsync("---\n");
|
||||
await writer.WriteAsync(yamlSerializer.Serialize(content.Metadata));
|
||||
await writer.WriteAsync("---\n");
|
||||
await writer.WriteAsync("<!--more-->\n");
|
||||
|
||||
if (isDraft)
|
||||
{
|
||||
await writer.WriteLineAsync("<!--more-->");
|
||||
}
|
||||
else
|
||||
{
|
||||
await writer.WriteAsync(content.FileContent);
|
||||
}
|
||||
}
|
||||
|
||||
private async Task<ConcurrentBag<BlogContent>> ScanContentsInternal(DirectoryInfo directory)
|
||||
|
@ -96,6 +110,79 @@ public class EssayScanService(
|
|||
return contents;
|
||||
}
|
||||
|
||||
public async Task<ImageScanResult> ScanImages()
|
||||
{
|
||||
BlogContents contents = await ScanContents();
|
||||
ValidateDirectory(_blogOptions.Root, out DirectoryInfo drafts, out DirectoryInfo posts);
|
||||
|
||||
List<FileInfo> unusedFiles = [];
|
||||
List<FileInfo> notFoundFiles = [];
|
||||
|
||||
ImageScanResult draftResult = await ScanUnusedImagesInternal(contents.Drafts, drafts);
|
||||
ImageScanResult postResult = await ScanUnusedImagesInternal(contents.Posts, posts);
|
||||
|
||||
unusedFiles.AddRange(draftResult.UnusedImages);
|
||||
notFoundFiles.AddRange(draftResult.NotFoundImages);
|
||||
unusedFiles.AddRange(postResult.UnusedImages);
|
||||
notFoundFiles.AddRange(postResult.NotFoundImages);
|
||||
|
||||
return new ImageScanResult(unusedFiles, notFoundFiles);
|
||||
}
|
||||
|
||||
private static Task<ImageScanResult> ScanUnusedImagesInternal(IEnumerable<BlogContent> contents,
|
||||
DirectoryInfo root)
|
||||
{
|
||||
Regex imageRegex = ImageRegex();
|
||||
ConcurrentBag<FileInfo> unusedImage = [];
|
||||
ConcurrentBag<FileInfo> notFoundImage = [];
|
||||
|
||||
Parallel.ForEach(contents, content =>
|
||||
{
|
||||
MatchCollection result = imageRegex.Matches(content.FileContent);
|
||||
DirectoryInfo imageDirectory = new(Path.Combine(root.FullName, content.FileName));
|
||||
|
||||
Dictionary<string, bool> usedDictionary;
|
||||
|
||||
if (imageDirectory.Exists)
|
||||
{
|
||||
usedDictionary = (from file in imageDirectory.EnumerateFiles()
|
||||
select new KeyValuePair<string, bool>(file.FullName, false)).ToDictionary();
|
||||
}
|
||||
else
|
||||
{
|
||||
usedDictionary = [];
|
||||
}
|
||||
|
||||
foreach (Match match in result)
|
||||
{
|
||||
string imageName = match.Groups[1].Value;
|
||||
|
||||
FileInfo usedFile = imageName.Contains(content.FileName)
|
||||
? new FileInfo(Path.Combine(root.FullName, imageName))
|
||||
: new FileInfo(Path.Combine(root.FullName, content.FileName, imageName));
|
||||
|
||||
if (usedDictionary.TryGetValue(usedFile.FullName, out _))
|
||||
{
|
||||
usedDictionary[usedFile.FullName] = true;
|
||||
}
|
||||
else
|
||||
{
|
||||
notFoundImage.Add(usedFile);
|
||||
}
|
||||
}
|
||||
|
||||
foreach (KeyValuePair<string, bool> pair in usedDictionary.Where(p => !p.Value))
|
||||
{
|
||||
unusedImage.Add(new FileInfo(pair.Key));
|
||||
}
|
||||
});
|
||||
|
||||
return Task.FromResult(new ImageScanResult(unusedImage.ToList(), notFoundImage.ToList()));
|
||||
}
|
||||
|
||||
[GeneratedRegex(@"\!\[.*?\]\((.*?)\)")]
|
||||
private static partial Regex ImageRegex();
|
||||
|
||||
private void ValidateDirectory(string root, out DirectoryInfo drafts, out DirectoryInfo posts)
|
||||
{
|
||||
root = Path.Combine(Environment.CurrentDirectory, root);
|
||||
|
|
|
@ -81,6 +81,14 @@ public static class CommandExtensions
|
|||
|
||||
newCommand.SetHandler(async (file, _, _, essayScanService) =>
|
||||
{
|
||||
BlogContents contents = await essayScanService.ScanContents();
|
||||
|
||||
if (contents.Posts.Any(content => content.FileName == file))
|
||||
{
|
||||
Console.WriteLine("There exists the same title blog in posts.");
|
||||
return;
|
||||
}
|
||||
|
||||
await essayScanService.SaveBlogContent(new BlogContent
|
||||
{
|
||||
FileName = file,
|
||||
|
@ -96,23 +104,113 @@ public static class CommandExtensions
|
|||
public static void AddListCommand(this RootCommand rootCommand)
|
||||
{
|
||||
Command command = new("list", "List all blogs");
|
||||
rootCommand.Add(command);
|
||||
rootCommand.AddCommand(command);
|
||||
|
||||
command.SetHandler(async (_, _, essyScanService) =>
|
||||
{
|
||||
BlogContents contents = await essyScanService.ScanContents();
|
||||
|
||||
Console.WriteLine($"All {contents.Posts.Count} Posts:");
|
||||
foreach (BlogContent content in contents.Posts)
|
||||
foreach (BlogContent content in contents.Posts.OrderBy(x => x.FileName))
|
||||
{
|
||||
Console.WriteLine($" - {content.FileName}");
|
||||
}
|
||||
|
||||
Console.WriteLine($"All {contents.Drafts.Count} Drafts:");
|
||||
foreach (BlogContent content in contents.Drafts)
|
||||
foreach (BlogContent content in contents.Drafts.OrderBy(x => x.FileName))
|
||||
{
|
||||
Console.WriteLine($" - {content.FileName}");
|
||||
}
|
||||
}, new BlogOptionsBinder(), new LoggerBinder<EssayScanService>(), new EssayScanServiceBinder());
|
||||
}
|
||||
|
||||
public static void AddScanCommand(this RootCommand rootCommand)
|
||||
{
|
||||
Command command = new("scan", "Scan unused and not found images.");
|
||||
rootCommand.AddCommand(command);
|
||||
|
||||
Option<bool> removeOption =
|
||||
new(name: "--rm", description: "Remove unused images.", getDefaultValue: () => false);
|
||||
command.AddOption(removeOption);
|
||||
|
||||
command.SetHandler(async (_, _, essayScanService, removeOptionValue) =>
|
||||
{
|
||||
ImageScanResult result = await essayScanService.ScanImages();
|
||||
|
||||
if (result.UnusedImages.Count != 0)
|
||||
{
|
||||
Console.WriteLine("Found unused images:");
|
||||
Console.WriteLine("HINT: use '--rm' to remove unused images.");
|
||||
}
|
||||
|
||||
foreach (FileInfo image in result.UnusedImages)
|
||||
{
|
||||
Console.WriteLine($" - {image.FullName}");
|
||||
}
|
||||
|
||||
if (removeOptionValue)
|
||||
{
|
||||
foreach (FileInfo image in result.UnusedImages)
|
||||
{
|
||||
image.Delete();
|
||||
}
|
||||
}
|
||||
|
||||
Console.WriteLine("Used not existed images:");
|
||||
|
||||
foreach (FileInfo image in result.NotFoundImages)
|
||||
{
|
||||
Console.WriteLine($" - {image.FullName}");
|
||||
}
|
||||
}, new BlogOptionsBinder(), new LoggerBinder<EssayScanService>(), new EssayScanServiceBinder(), removeOption);
|
||||
}
|
||||
|
||||
public static void AddPublishCommand(this RootCommand rootCommand)
|
||||
{
|
||||
Command command = new("publish", "Publish a new blog file.");
|
||||
rootCommand.AddCommand(command);
|
||||
|
||||
Argument<string> filenameArgument = new(name: "blog name", description: "The published blog filename.");
|
||||
command.AddArgument(filenameArgument);
|
||||
|
||||
command.SetHandler(async (blogOptions, _, essayScanService, filename) =>
|
||||
{
|
||||
BlogContents contents = await essayScanService.ScanContents();
|
||||
|
||||
BlogContent? content = (from blog in contents.Drafts
|
||||
where blog.FileName == filename
|
||||
select blog).FirstOrDefault();
|
||||
|
||||
if (content is null)
|
||||
{
|
||||
Console.WriteLine("Target blog does not exist.");
|
||||
return;
|
||||
}
|
||||
|
||||
// 将选中的博客文件复制到posts
|
||||
await essayScanService.SaveBlogContent(content, isDraft: false);
|
||||
|
||||
// 复制图片文件夹
|
||||
DirectoryInfo sourceImageDirectory =
|
||||
new(Path.Combine(blogOptions.Value.Root, "drafts", content.FileName));
|
||||
DirectoryInfo targetImageDirectory =
|
||||
new(Path.Combine(blogOptions.Value.Root, "posts", content.FileName));
|
||||
|
||||
if (sourceImageDirectory.Exists)
|
||||
{
|
||||
targetImageDirectory.Create();
|
||||
foreach (FileInfo file in sourceImageDirectory.EnumerateFiles())
|
||||
{
|
||||
file.CopyTo(Path.Combine(targetImageDirectory.FullName, file.Name), true);
|
||||
}
|
||||
|
||||
sourceImageDirectory.Delete(true);
|
||||
}
|
||||
|
||||
// 删除原始的文件
|
||||
FileInfo sourceBlogFile = new(Path.Combine(blogOptions.Value.Root, "drafts", content.FileName + ".md"));
|
||||
sourceBlogFile.Delete();
|
||||
}, new BlogOptionsBinder(),
|
||||
new LoggerBinder<EssayScanService>(), new EssayScanServiceBinder(), filenameArgument);
|
||||
}
|
||||
}
|
||||
|
|
|
@ -7,5 +7,7 @@ rootCommand.AddServeCommand();
|
|||
rootCommand.AddNewCommand();
|
||||
rootCommand.AddListCommand();
|
||||
rootCommand.AddWatchCommand();
|
||||
rootCommand.AddScanCommand();
|
||||
rootCommand.AddPublishCommand();
|
||||
|
||||
await rootCommand.InvokeAsync(args);
|
||||
|
|
0
YaeBlog/source/drafts/.gitkeep
Normal file
0
YaeBlog/source/drafts/.gitkeep
Normal file
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
title: test-essay
|
||||
date: 2024-08-22T22:31:34.3177253+08:00
|
||||
tags:
|
||||
---
|
||||
<!--more-->
|
0
YaeBlog/source/posts/.gitkeep
Normal file
0
YaeBlog/source/posts/.gitkeep
Normal file
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战第五篇 ArchLinux标准安装流程
|
||||
title: 日用Linux挑战 第5篇 标准安装流程
|
||||
date: 2024-7-16 20:08:37
|
||||
tags:
|
||||
- Linux
|
||||
|
|
|
@ -44,7 +44,7 @@ date: 2022-07-27 11:34:49
|
|||
|
||||
而且采用 `Git`还有一个好处,采用 `Github`的 `Insight`功能可以轻松的看出大家的贡献值()。
|
||||
|
||||
![img](1.png "贡献")
|
||||
![img](1.png)
|
||||
|
||||
## 一些技术上的收获
|
||||
|
||||
|
|
232
YaeBlog/source/posts/build-dotnet-from-source.md
Normal file
232
YaeBlog/source/posts/build-dotnet-from-source.md
Normal file
|
@ -0,0 +1,232 @@
|
|||
---
|
||||
title: 交叉编译.NET到RISC-V平台
|
||||
date: 2024-08-25T15:41:05.9519941+08:00
|
||||
tags:
|
||||
- dotnet
|
||||
- 技术笔记
|
||||
---
|
||||
|
||||
|
||||
我们编译是这样的,在本平台上编译只要敲三条命令就好了,而交叉编译要考虑的就很多了。
|
||||
|
||||
<!--more-->
|
||||
|
||||
这次我们打算在`x86_64`平台上交叉编译`.NET`到`riscv64`平台上。
|
||||
|
||||
首先从相关的[进度跟踪页面](https://github.com/dotnet/runtime/issues/84834)显示,.NET移植到RISC-V的进度还远远没有完成,但是在整个SDK中除了AOT编译器的部分都可以在RISC-V平台上编译了。
|
||||
|
||||
## 环境准备
|
||||
|
||||
我们构建的环境是Arch Linux,因此依赖包的安装使用`pacman`进行。综合[.NET官方文档](https://github.com/dotnet/runtime/blob/main/docs/workflow/requirements/linux-requirements.md)给出的信息和Arch Linux官方打包的脚本,所需要安装的软件包如下:
|
||||
|
||||
| 包名 | 备注 |
|
||||
| ------------- | ------------------------------------------------------------ |
|
||||
| bash | |
|
||||
| clang | |
|
||||
| lld | |
|
||||
| cmake | |
|
||||
| git | |
|
||||
| icu | 第一次看见这个名词就想吐槽,谁TM想得到重症监护室会是一个全球化支持库,, |
|
||||
| inetutils | 常见的网络工具库,官方文档没有但是构建脚本有 |
|
||||
| krb5 | 一个网络通信认证库?不懂 |
|
||||
| libgit2 | |
|
||||
| libunwind | 解析程序运行堆栈的魔法工具 |
|
||||
| libxml2 | |
|
||||
| lldb | |
|
||||
| llvm | |
|
||||
| lttng-ust2.12 | 又是一个跟踪运行的魔法工具 |
|
||||
| openssl | |
|
||||
| systemd | |
|
||||
| zlib | |
|
||||
|
||||
### 交叉编译工具链
|
||||
|
||||
在正式开始编译.NET之前,先学习如何搭建一套C/C++的交叉编译工具链。
|
||||
|
||||
通常一份GNU工具链只能针对一个平台进行编译,但是LLVM工具链是一套先天的交叉编译工具链,例如对于`llc`工具,使用`llc --version`命令可以看见该编译器可以生成多种目标平台上的汇编代码:
|
||||
|
||||
![image-20240824120646587](./build-dotnet-from-source/image-20240824120646587.png)
|
||||
|
||||
在使用`clang++`时加上`--target=<triple>`指定目标三元组就可以进行交叉编译。
|
||||
|
||||
但是直接使用`clang++ --target=riscv64-linux-gnu hello.cpp -o hello`时会爆出一个奇怪的找不到头文件错误:
|
||||
|
||||
```cpp
|
||||
// File: hello.cpp
|
||||
#include <iostream>
|
||||
|
||||
int main()
|
||||
{
|
||||
std::cout << "Hello, world!" << std::endl;
|
||||
return 0;
|
||||
}
|
||||
```
|
||||
|
||||
![image-20240824121425007](./build-dotnet-from-source/image-20240824121425007.png)
|
||||
|
||||
看样子交叉编译也不是开箱即用的。最开始我们猜想系统提供的LLVM工具链没有被配置为交叉编译,因此尝试在本地自行编译一套LLVM工具链。
|
||||
|
||||
首先从[Github Release](https://github.com/llvm/llvm-project/releases)上下载最新的`llvm-project`源代码并解压到本地文件夹中。这里126M的压缩文件可以解压出一个1.8G大小的源代码文件夹。创建一个`build`文件夹,在该文件夹使用如下的配置进行编译,在配置中使用`LLVM_TARGETS_TO_BUILD`选择启用`X86`和`RISCV`的支持。
|
||||
|
||||
```bash
|
||||
cmake ../llvm-project.src/llvm \
|
||||
-DCMAKE_BUILD_TYPE=Release \
|
||||
-DCMAKE_C_COMPILER=clang \
|
||||
-DCMAKE_CXX_COMPILER=clang++ \
|
||||
-DLLVM_TARGETS_TO_BUILD="X86;RISCV" \
|
||||
-DLLVM_ENABLE_PROJECTS="clang;lld;clang-tools-extra"
|
||||
make
|
||||
sudo make install
|
||||
```
|
||||
|
||||
编译之后的成果会安装到`/usr/local/`目录下,而在`$PATH`环境变量中`/usr/local`位置将在`/usr`目录之前,因此调用时将会优先调用我们自行编译的LLVM工具链,而不是系统中安装的LLVM工具链。
|
||||
|
||||
![image-20240824134158262](./build-dotnet-from-source/image-20240824134158262.png)
|
||||
|
||||
但是使用这套编译工具链仍然会爆出和之前一样的问题。说明这并不是系统安装LLVM工具链的问题。仔细一想也确实,这里提示找不到对应的头文件应该是找不到RISC-V架构之下的头文件——这里的也是交叉编译的主要问题所在:虽然LLVM工具链宣称自己是原生支持交叉编译的,但是没人宣称说标准库和头文件是原生的。这里我们就需要一个根文件系统来提供这些头文件和各种库文件。
|
||||
|
||||
### 生成根文件系统
|
||||
|
||||
在.NET的构建文档中提供了一个自动生成头文件的脚本,但是这个脚本似乎强依赖某个U开头的发行版,身为Arch神教信徒的我似乎没有办法使用。直接使用预构建好的镜像又屏蔽了太多的技术细节,感觉也不太好。因此打算尝试使用[arch-riscv](https://mirror.iscas.ac.cn/archriscv/)提供的移植Arch Linux系统作为根文件系统。
|
||||
|
||||
首先使用移植之后的根文件系统构建一个`archriscv`镜像:
|
||||
|
||||
```Dockerfile
|
||||
FROM archriscv AS bootstrap
|
||||
|
||||
COPY etc /rootfs
|
||||
COPY bootstrap/pacstrap-docker /usr/local/bin/
|
||||
RUN pacstrap-docker /rootfs base
|
||||
RUN rm /rootfs/var/lib/pacman/sync/*
|
||||
|
||||
FROM scratch AS root
|
||||
|
||||
COPY --from=bootstrap /rootfs /
|
||||
COPY etc /etc
|
||||
|
||||
LABEL org.opencontainers.image.title="Arch Linux RISC-V"
|
||||
LABEL org.opencontainers.image.description="This is an Arch Linux port to the RISC-V architecture."
|
||||
|
||||
ENV LANG=en_US.UTF-8
|
||||
RUN ldconfig && locale-gen
|
||||
RUN pacman-key --init && \
|
||||
pacman-key --populate && \
|
||||
bash -c "rm -rf etc/pacman.d/gnupg/{openpgp-revocs.d/,private-keys-v1.d/,pubring.gpg~,gnupg.S.}*"
|
||||
|
||||
CMD ["/usr/bin/bash"]
|
||||
```
|
||||
|
||||
虽然这个镜像是一个自举的镜像,给出这个构建文件似乎没有什么用处(笑)。再在这个镜像的基础上新建一层镜像安装各种.NET的依赖项。
|
||||
|
||||
```dockerfile
|
||||
FROM archriscv
|
||||
|
||||
RUN pacman -Syyu --noconfirm bash clang cmake git icu inetutils \
|
||||
krb5 libgit2 libunwind libxml2 lldb llvm lttng-ust2.12 \
|
||||
openssl systemd zlib
|
||||
```
|
||||
|
||||
构建这个镜像,再将这个镜像根目录下的所有文件拷贝出来。
|
||||
|
||||
```bash
|
||||
docker build . --platform linux/riscv64 -t archriscv:base-devel
|
||||
mkdir rootfs
|
||||
cid=$(docker run -d --platform linux/riscv64 archriscv:base-devel)
|
||||
sudo docker cp $cid:/ rootfs
|
||||
sudo chown $USER:$USER -R rootfs
|
||||
```
|
||||
|
||||
新建一个`runtime-build`文件夹,使用下面的指令在`rootfs`文件系统中构建`libcxx`和`compiler-rt`。
|
||||
|
||||
> `libcxx`和`compiler-rt`不是常规交叉编译需要的,而是编译.NET所需要的。
|
||||
|
||||
```bash
|
||||
export TARGET_TRIPLE="riscv64-linux-gnu"
|
||||
export CLANG_MAJOR_VERSION=18
|
||||
export ROOTFS_DIR=<ROOTFS>
|
||||
cmake -S ../llvm-project.src/runtimes \
|
||||
-DCMAKE_BUILD_TYPE=Release \
|
||||
-DCMAKE_ASM_COMPILER=clang \
|
||||
-DCMAKE_C_COMPILER=clang \
|
||||
-DCMAKE_CXX_COMPILER=clang++ \
|
||||
-DCMAKE_ASM_COMPILER_TARGET="$TARGET_TRIPLE" \
|
||||
-DCMAKE_C_COMPILER_TARGET="$TARGET_TRIPLE" \
|
||||
-DCMAKE_CXX_COMPILER_TARGET="$TARGET_TRIPLE" \
|
||||
-DCMAKE_POSITION_INDEPENDENT_CODE=ON \
|
||||
-DCMAKE_SYSROOT="$ROOTFS_DIR" \
|
||||
-DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=lld" \
|
||||
-DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM="NEVER" \
|
||||
-DLLVM_USE_LINKER=lld \
|
||||
-DLLVM_ENABLE_RUNTIMES="libcxx;compiler-rt" \
|
||||
-DLIBCXX_ENABLE_SHARED=OFF \
|
||||
-DLIBCXX_CXX_ABI=libstdc++ \
|
||||
-DLIBCXX_CXX_ABI_INCLUDE_PATHS="$ROOTFS_DIR/usr/include/c++/14.2.1/;$ROOTFS_DIR/usr/include/c++/14.2.1/riscv64-unknown-linux-gnu/" \
|
||||
-DCOMPILER_RT_CXX_LIBRARY="libcxx" \
|
||||
-DCOMPILER_RT_STATIC_CXX_LIBRARY=ON \
|
||||
-DCOMPILER_RT_BUILD_SANITIZERS=OFF \
|
||||
-DCOMPILER_RT_BUILD_MEMPROF=OFF \
|
||||
-DCOMPILER_RT_BUILD_LIBFUZZER=OFF \
|
||||
-DCOMPILER_RT_DEFAULT_TARGET_ONLY=ON \
|
||||
-DCOMPILER_RT_INSTALL_PATH="/usr/local/lib/clang/$CLANG_MAJOR_VERSION"
|
||||
make -j20
|
||||
sudo cmake --install . --prefix "$ROOTFS_DIR/usr"
|
||||
```
|
||||
|
||||
在构建指令中需要根据安装的`gcc`版本调整`_DLIBCXX_CXX_ABI_INCLUDE_PATHS`的路径。
|
||||
|
||||
完成所有上述的工作之后,回到我们最开始的你好世界样例,使用下面这行神秘的代码进行编译:
|
||||
|
||||
```bash
|
||||
clang++ --target=riscv64-linux-gnu --sysroot=$ROOTFS_DIR -fuse-ld=lld hello.cpp -o hello
|
||||
```
|
||||
|
||||
这次编译不会出现问题,上面指定的三个参数依次为指定目标三元组、指定根文件系统的位置和指定使用`lld`作为链接器。使用Docker镜像进行测试确认编译之后的二进制文件可以正常运行。
|
||||
|
||||
### 复盘
|
||||
|
||||
在正式开始下一步之前,我们先复盘一下在搭建交叉编译环境时我们都做了什么:
|
||||
|
||||
- 使用`LLVM_TARGETS_TO_BUILD`编译了一套新的LLVM,
|
||||
- 将安装了基础依赖包的`archriscv`导出作为根文件系统,
|
||||
- 使用该根文件系统在该根文件系统中编译了`libcxx`和`compiler-rt`两个库。
|
||||
|
||||
这三步也带来了三个问题:
|
||||
|
||||
1. Arch Linux自带的LLVM工具链难道不能交叉编译吗?
|
||||
2. Arch Linux 官方提供的`riscv64-linux-gnu-gcc`包能够作为根文件系统吗?
|
||||
3. 能够在上述的根文件系统中安装我们需要的`libcxx`和`compiler-rt`两个库吗?
|
||||
|
||||
第一个问题的回答是Arch Linux安装的LLVM工具是可以交叉编译的。虽然在Arch Linux官方构建LLVM工具链的[构建脚本](https://gitlab.archlinux.org/archlinux/packaging/packages/clang/-/blob/main/PKGBUILD?ref_type=heads)中没有使用`LLVM_TARGETS_TO_BUILD`参数,但是这个参数的默认值是`all`。这一点我们也可以通过实验来验证。
|
||||
|
||||
![image-20240824153514149](./build-dotnet-from-source/image-20240824153514149.png)于是回到编译`llvm`的目录下执行`cat install_manifest.txt | sudo xargs rm`。
|
||||
|
||||
第二个问题的回答可以使用实验来验证,首先安装`riscv64-linux-gnu-gcc`,然后将根文件系统的位置设置为`/usr/riscv64-linux-gnu`,重新编译上面的你好世界样例。编译之后可以正常执行。
|
||||
|
||||
第三个问题的回答是还是新建一个根文件系统罢,随便往系统目录里面写东西感觉是一个不太好的习惯。
|
||||
|
||||
## 正式编译
|
||||
|
||||
首先进入克隆代码的目录,运行初始化脚本。
|
||||
|
||||
```bash
|
||||
cd dotnet
|
||||
./prep-source-build.sh
|
||||
```
|
||||
|
||||
设置根文件系统的目录,这里仍然使用从安装了`base-devel`的Docker容器中导出并自行编译了`compiler-rt`和`libcxx`的根文件系统。
|
||||
|
||||
```bash
|
||||
export ROOTFS_DIR=<rootfs>
|
||||
```
|
||||
|
||||
然后使用下面这条神秘的命令开始交叉编译:
|
||||
|
||||
```bash
|
||||
./build.sh -sb --clean-while-building /p:TargetOS=linux /p:TargetArchitecture=riscv64 /p:Crossbuild=true /p:BuildArgs="/p:BundleNativeAotCompiler=false"
|
||||
```
|
||||
|
||||
上面的第一个参数是指定了`source-build`选项,第二个参数指定了在编译的过程中清理不需要的文件以节省硬盘空间,后面的几个MSBUILD参数则是指定为RISC-V架构上的Linux系统构建,并且不构建AOT编译器。
|
||||
|
||||
但是现在的.NET在RISC-V平台上还是废物一个,甚至连`dotnet new`都跑不过,下一步看看能不能运行一下运行时的测试集看看。
|
||||
|
||||
![image-20240824214145759](./build-dotnet-from-source/image-20240824214145759.png)
|
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824120646587.png
(Stored with Git LFS)
Normal file
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824120646587.png
(Stored with Git LFS)
Normal file
Binary file not shown.
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824121425007.png
(Stored with Git LFS)
Normal file
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824121425007.png
(Stored with Git LFS)
Normal file
Binary file not shown.
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824134158262.png
(Stored with Git LFS)
Normal file
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824134158262.png
(Stored with Git LFS)
Normal file
Binary file not shown.
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824153514149.png
(Stored with Git LFS)
Normal file
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824153514149.png
(Stored with Git LFS)
Normal file
Binary file not shown.
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824214145759.png
(Stored with Git LFS)
Normal file
BIN
YaeBlog/source/posts/build-dotnet-from-source/image-20240824214145759.png
(Stored with Git LFS)
Normal file
Binary file not shown.
BIN
YaeBlog/source/posts/compile-mediapipe/2023-01-19-20-21-30-Screenshot_20230119_202008.png
(Stored with Git LFS)
BIN
YaeBlog/source/posts/compile-mediapipe/2023-01-19-20-21-30-Screenshot_20230119_202008.png
(Stored with Git LFS)
Binary file not shown.
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战 第0篇
|
||||
title: 日用Linux挑战 第0篇 初见Arch Linux
|
||||
tags:
|
||||
- Linux
|
||||
- 随笔
|
||||
|
|
BIN
YaeBlog/source/posts/daily-linux-0/2023-01-12-13-28-11-Screenshot_20230112_132756.png
(Stored with Git LFS)
BIN
YaeBlog/source/posts/daily-linux-0/2023-01-12-13-28-11-Screenshot_20230112_132756.png
(Stored with Git LFS)
Binary file not shown.
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战第1篇
|
||||
title: 日用Linux挑战 第1篇 问题与挑战
|
||||
tags:
|
||||
- Linux
|
||||
- 随笔
|
||||
|
@ -45,7 +45,7 @@ date: 2023-03-08 22:37:29
|
|||
|
||||
简单的说,我不认为现在`Linux`已经准备好切换到`Wayland`下了。
|
||||
|
||||
> 听说最精`Ubuntu 22.04`已经默认使用`Wayland`作为显示协议了,等我有了其他的电脑可以试一试,看看商业公司的加入能不能带来一点转机。
|
||||
> 听说最新的`Ubuntu 22.04`已经默认使用`Wayland`作为显示协议了,等我有了其他的电脑可以试一试,看看商业公司的加入能不能带来一点转机。
|
||||
|
||||
## 使用中发现的问题
|
||||
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战 第2篇
|
||||
title: 日用Linux挑战 第2篇 Wayland
|
||||
tags:
|
||||
- 随笔
|
||||
- Linux
|
||||
|
|
BIN
YaeBlog/source/posts/daily-linux-2/image-20230720202327220.png
(Stored with Git LFS)
BIN
YaeBlog/source/posts/daily-linux-2/image-20230720202327220.png
(Stored with Git LFS)
Binary file not shown.
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战 第三篇
|
||||
title: 日用Linux挑战 第3篇 放弃Wayland
|
||||
tags:
|
||||
- 随笔
|
||||
- Linux
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 日用Linux挑战 第四篇
|
||||
title: 日用Linux挑战 第4篇 新的开始
|
||||
tags:
|
||||
- Linux
|
||||
- 随笔
|
||||
|
|
|
@ -44,7 +44,7 @@ bool ParserBoolValue(string input)
|
|||
}
|
||||
```
|
||||
|
||||
这就是一个**解析器(Parser)**的原型实现:输入需要识别的字符串,输出识别的结果。在这个原型方法中,我们可以很容易发现两个问题:
|
||||
这就是一个 **解析器(Parser)** 的原型实现:输入需要识别的字符串,输出识别的结果。在这个原型方法中,我们可以很容易发现两个问题:
|
||||
|
||||
1. 解析器并不会**消耗**输入的字符串,缺少一个读取字符串的游标。
|
||||
2. 解析器输出结果的方式并不高明,输出的结果只能是解析成功情况的结果,解析失败的情况需要通过抛出一个自定义的异常`InvalidInputException`,但是考虑到一个解析器解析失败是非常常见的情况,在这里使用异常方式返回错误结果会导致非常严重的性能问题。
|
||||
|
@ -64,7 +64,7 @@ public abstract class Parser<T>
|
|||
|
||||
上面解析器基类中,类上的泛型参数`T`表示该解析器最终解析结果的类型,解析函数`Parse`的泛型参数`TState`是实现了输入状态`IReadState`的类型,返回的类型`ParseResult`就是上文中提到的解析结果基类。
|
||||
|
||||
在设计完解析器之后,该谈一谈**组合子(Combinator)**了。实际上组合子就是将多个解析器组合到一起的一系列函数,输入一个或者多个解析器,输出一个合并之后的解析器。容易想到,各种解析器组合在一起的方式千千万万,但是实际上我们只需要实现一系列基本的组合子,就可以通过综合使用各种解析器和组合子将各种需要的解析器和组合子实现出现。实际上,这也是解析器组合子思想的集中体现,通过基础的“砖块”(解析器)和“水泥“(组合子)设计和实现各种构建,最终建造出宏伟的高楼。
|
||||
在设计完解析器之后,该谈一谈 **组合子(Combinator)** 了。实际上组合子就是将多个解析器组合到一起的一系列函数,输入一个或者多个解析器,输出一个合并之后的解析器。容易想到,各种解析器组合在一起的方式千千万万,但是实际上我们只需要实现一系列基本的组合子,就可以通过综合使用各种解析器和组合子将各种需要的解析器和组合子实现出现。实际上,这也是解析器组合子思想的集中体现,通过基础的“砖块”(解析器)和“水泥“(组合子)设计和实现各种构建,最终建造出宏伟的高楼。
|
||||
|
||||
基础解析器和组合子的选择因人而异,但是一个常见的组合是:
|
||||
|
||||
|
|
|
@ -55,7 +55,7 @@ cert: false
|
|||
在进行了这些更改之后,我们再次输入code-server重启服务,如果一次顺利,我们可以看见以下的启动信息
|
||||
![启动信息](./vscode-in-browser/1.png)
|
||||
我们可以打开浏览器,在地址栏中输入你的服务器公网IP加上你自己设置的端口号,就可以打开自己的VSCode Online界面了。
|
||||
![主界面](./vscode-in-browser/1.png)
|
||||
![主界面](./vscode-in-browser/2.png)
|
||||
输入自己的设置密码,就可以开始把浏览器中的VSCode当作自己本地计算机上的VSCode使用了,不过其中的文件是位于自己的服务器上的。
|
||||
>如果你和我一样使用的阿里云的服务器,可能还需要到服务器的管理界面设置安全组放行相应的端口,具体参考[这篇文章](https://help.aliyun.com/document_detail/59086.html?spm=5176.10173289.help.dexternal.4ff02e77892BZP)
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user