登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
Gitee AI
NEW
我知道了
查看详情
登录
注册
9月25日晚8点,Gitee 吐槽大会正式开幕,吐槽火力全开,Gitee 接招不慌!
代码拉取完成,页面将自动刷新
开源项目
>
开发工具
>
编译/构建/部署
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
1.5K
Star
7.6K
Fork
1.4K
GVP
方舟编译器
/
OpenArkCompiler
代码
Issues
197
Pull Requests
14
Wiki
统计
流水线
服务
Gitee Pages
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
我知道了,不再自动展开
更新失败,请稍后重试!
Issues
/
详情
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
build mplfe using same set of header files
已完成
#I3I01V
HuWen
成员
创建于
2021-04-09 05:06
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。 鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。 链接用到的clang/llvm库也需要放到 ThirdParty/ ``` diff --git a/build/config.gni b/build/config.gni index f6ce5124..14bcc9b1 100644 --- a/build/config.gni +++ b/build/config.gni @@ -19,9 +19,8 @@ if (OLD_OS == "1") { } else { CLANG_PATH = "/usr" } -LLVMINC = "${CLANG_PATH}/include" LLVMLIBDIR = "${CLANG_PATH}/lib" -CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src" +CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src" CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src" ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc" diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn index e5eb1899..39778047 100644 --- a/src/mplfe/BUILD.gn +++ b/src/mplfe/BUILD.gn @@ -40,7 +40,8 @@ include_directories = [ "${MAPLE_ROOT}/third_party/bounds_checking_function/include", "${MPLFE_ROOT}/ast_input/include", "${MPLFE_ROOT}/ast_input/lib", - "${LLVMINC}", + "//../ThirdParty/cfe-8.0.0.src/include", + "//../ThirdParty/llvm-8.0.0.src/include", "//../ThirdParty/cfe-8.0.0.src/tools", ] ``` @binaryfz @QunYeNB
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。 鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。 链接用到的clang/llvm库也需要放到 ThirdParty/ ``` diff --git a/build/config.gni b/build/config.gni index f6ce5124..14bcc9b1 100644 --- a/build/config.gni +++ b/build/config.gni @@ -19,9 +19,8 @@ if (OLD_OS == "1") { } else { CLANG_PATH = "/usr" } -LLVMINC = "${CLANG_PATH}/include" LLVMLIBDIR = "${CLANG_PATH}/lib" -CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src" +CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src" CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src" ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc" diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn index e5eb1899..39778047 100644 --- a/src/mplfe/BUILD.gn +++ b/src/mplfe/BUILD.gn @@ -40,7 +40,8 @@ include_directories = [ "${MAPLE_ROOT}/third_party/bounds_checking_function/include", "${MPLFE_ROOT}/ast_input/include", "${MPLFE_ROOT}/ast_input/lib", - "${LLVMINC}", + "//../ThirdParty/cfe-8.0.0.src/include", + "//../ThirdParty/llvm-8.0.0.src/include", "//../ThirdParty/cfe-8.0.0.src/tools", ] ``` @binaryfz @QunYeNB
评论 (
0
)
HuWen
创建了
任务
HuWen
将
关联仓库
设置为
方舟编译器/OpenArkCompiler
HuWen
将
置顶等级
设置为
高
HuWen
修改了
描述
原值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译
不过
的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
ubuntu 20.04 需要先安装 libclang-dev, 它会同时安装 libclang-10-dev
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..f46c7895 100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -17,11 +17,10 @@
if (OLD_OS == "1") {
CLANG_PATH = "${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04"
} else {
- CLANG_PATH = "/usr"
+ CLANG_PATH = "/usr/lib/llvm-10"
}
-LLVMINC = "${CLANG_PATH}/include"
LLVMLIBDIR = "${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.gn
@@ -40,7 +40,8 @@ include_directories = [
"${MAPLE_ROOT}/third_party/bounds_checking_function/include",
"${MPLFE_ROOT}/ast_input/include",
"${MPLFE_ROOT}/ast_input/lib",
- "${LLVMINC}",
+ "//../ThirdParty/cfe-8.0.0.src/include",
+ "//../ThirdParty/llvm-8.0.0.src/include",
"//../ThirdParty/cfe-8.0.0.src/tools",
]
diff --git a/tools/setup_tools.sh b/tools/setup_tools.sh
index 2583de33..2fc31b9d 100755
--- a/tools/setup_tools.sh
+++ b/tools/setup_tools.sh
@@ -174,10 +174,10 @@ if [ "$OLD_OS" == "1" ]; then
ln -s -f ${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f /usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
else
- ln -s -f /usr/bin/clang++ ${TOOL_BIN_PATH}/clang++
- ln -s -f /usr/bin/clang ${TOOL_BIN_PATH}/clang
- ln -s -f /usr/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
- ln -s -f /usr/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
+ ln -s -f /usr/lib/llvm-10/bin/clang++ ${TOOL_BIN_PATH}/clang++
+ ln -s -f /usr/lib/llvm-10/bin/clang ${TOOL_BIN_PATH}/clang
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f ${MAPLE_ROOT}/tools/qemu/package/usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
fi
ln -s -f ${MAPLE_ROOT}/tools/open64_prebuilt/x86/aarch64/bin/clangfe ${TOOL_BIN_PATH}/clangfe
```
@binaryfz @QunYeNB
新值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译
失败
的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
ubuntu 20.04 需要先安装 libclang-dev, 它会同时安装 libclang-10-dev
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..f46c7895 100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -17,11 +17,10 @@
if (OLD_OS == "1") {
CLANG_PATH = "${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04"
} else {
- CLANG_PATH = "/usr"
+ CLANG_PATH = "/usr/lib/llvm-10"
}
-LLVMINC = "${CLANG_PATH}/include"
LLVMLIBDIR = "${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.gn
@@ -40,7 +40,8 @@ include_directories = [
"${MAPLE_ROOT}/third_party/bounds_checking_function/include",
"${MPLFE_ROOT}/ast_input/include",
"${MPLFE_ROOT}/ast_input/lib",
- "${LLVMINC}",
+ "//../ThirdParty/cfe-8.0.0.src/include",
+ "//../ThirdParty/llvm-8.0.0.src/include",
"//../ThirdParty/cfe-8.0.0.src/tools",
]
diff --git a/tools/setup_tools.sh b/tools/setup_tools.sh
index 2583de33..2fc31b9d 100755
--- a/tools/setup_tools.sh
+++ b/tools/setup_tools.sh
@@ -174,10 +174,10 @@ if [ "$OLD_OS" == "1" ]; then
ln -s -f ${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f /usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
else
- ln -s -f /usr/bin/clang++ ${TOOL_BIN_PATH}/clang++
- ln -s -f /usr/bin/clang ${TOOL_BIN_PATH}/clang
- ln -s -f /usr/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
- ln -s -f /usr/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
+ ln -s -f /usr/lib/llvm-10/bin/clang++ ${TOOL_BIN_PATH}/clang++
+ ln -s -f /usr/lib/llvm-10/bin/clang ${TOOL_BIN_PATH}/clang
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f ${MAPLE_ROOT}/tools/qemu/package/usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
fi
ln -s -f ${MAPLE_ROOT}/tools/open64_prebuilt/x86/aarch64/bin/clangfe ${TOOL_BIN_PATH}/clangfe
```
@binaryfz @QunYeNB
HuWen
修改了
描述
原值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
ubuntu 20.04 需要先安装 libclang-dev, 它会同时安装 libclang-10-dev
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..f46c7895 100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -17,11 +17,10 @@
if (OLD_OS == "1") {
CLANG_PATH = "${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04"
} else {
- CLANG_PATH = "/usr"
+ CLANG_PATH = "/usr/lib/llvm-10"
}
-LLVMINC = "${CLANG_PATH}/include"
LLVMLIBDIR = "${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.gn
@@ -40,7 +40,8 @@ include_directories = [
"${MAPLE_ROOT}/third_party/bounds_checking_function/include",
"${MPLFE_ROOT}/ast_input/include",
"${MPLFE_ROOT}/ast_input/lib",
- "${LLVMINC}",
+ "//../ThirdParty/cfe-8.0.0.src/include",
+ "//../ThirdParty/llvm-8.0.0.src/include",
"//../ThirdParty/cfe-8.0.0.src/tools",
]
diff --git a/tools/setup_tools.sh b/tools/setup_tools.sh
index 2583de33..2fc31b9d 100755
--- a/tools/setup_tools.sh
+++ b/tools/setup_tools.sh
@@ -174,10 +174,10 @@ if [ "$OLD_OS" == "1" ]; then
ln -s -f ${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f /usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
else
- ln -s -f /usr/bin/clang++ ${TOOL_BIN_PATH}/clang++
- ln -s -f /usr/bin/clang ${TOOL_BIN_PATH}/clang
- ln -s -f /usr/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
- ln -s -f /usr/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
+ ln -s -f /usr/lib/llvm-10/bin/clang++ ${TOOL_BIN_PATH}/clang++
+ ln -s -f /usr/lib/llvm-10/bin/clang ${TOOL_BIN_PATH}/clang
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f ${MAPLE_ROOT}/tools/qemu/package/usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
fi
ln -s -f ${MAPLE_ROOT}/tools/open64_prebuilt/x86/aarch64/bin/clangfe ${TOOL_BIN_PATH}/clangfe
```
@binaryfz @QunYeNB
新值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
链接用到的clang/llvm库也需要放到 ThirdParty/
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..f46c7895 100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -17,11 +17,10 @@
if (OLD_OS == "1") {
CLANG_PATH = "${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04"
} else {
- CLANG_PATH = "/usr"
+ CLANG_PATH = "/usr/lib/llvm-10"
}
-LLVMINC = "${CLANG_PATH}/include"
LLVMLIBDIR = "${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SRC_DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.gn
@@ -40,7 +40,8 @@ include_directories = [
"${MAPLE_ROOT}/third_party/bounds_checking_function/include",
"${MPLFE_ROOT}/ast_input/include",
"${MPLFE_ROOT}/ast_input/lib",
- "${LLVMINC}",
+ "//../ThirdParty/cfe-8.0.0.src/include",
+ "//../ThirdParty/llvm-8.0.0.src/include",
"//../ThirdParty/cfe-8.0.0.src/tools",
]
diff --git a/tools/setup_tools.sh b/tools/setup_tools.sh
index 2583de33..2fc31b9d 100755
--- a/tools/setup_tools.sh
+++ b/tools/setup_tools.sh
@@ -174,10 +174,10 @@ if [ "$OLD_OS" == "1" ]; then
ln -s -f ${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f /usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
else
- ln -s -f /usr/bin/clang++ ${TOOL_BIN_PATH}/clang++
- ln -s -f /usr/bin/clang ${TOOL_BIN_PATH}/clang
- ln -s -f /usr/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
- ln -s -f /usr/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
+ ln -s -f /usr/lib/llvm-10/bin/clang++ ${TOOL_BIN_PATH}/clang++
+ ln -s -f /usr/lib/llvm-10/bin/clang ${TOOL_BIN_PATH}/clang
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f ${MAPLE_ROOT}/tools/qemu/package/usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
fi
ln -s -f ${MAPLE_ROOT}/tools/open64_prebuilt/x86/aarch64/bin/clangfe ${TOOL_BIN_PATH}/clangfe
```
@binaryfz @QunYeNB
HuWen
修改了
描述
原值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
链接用到的clang/llvm库也需要放到 ThirdParty/
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..
f
4
6
c
7895
100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -1
7
,
11 +17,10 @@
if (OLD_OS == "1") {
CLANG_PATH = "
${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04"
}
else {
-
CLA
N
G_PATH = "/usr"
+ CLANG_PATH
= "/usr/lib/llvm-10"
}
-LLVMIN
C
= "${CLANG_
P
ATH}/include"
LLVMLIBDIR =
"${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SRC
_
DIR = "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH = "${MAPLE_ROOT}/..
/
ThirdParty/cfe-8.0.0.src"
ANDROID_GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b/src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.g
n
@@
-40,7 +40,8 @@ include_directories = [
"${
MAPLE_ROOT}/third_party/bounds_checking_function/include",
"
${MPLFE_ROOT}/ast_input/include",
"
${MPLFE_ROOT}/ast_input/lib",
-
"
${LLVMINC}",
+ "//../ThirdParty/cfe-8.0.0.src/include",
+ "//../ThirdParty/llvm-8.0.0.src/include",
"//../ThirdParty/cfe-8.0.0.src/tools",
]
diff --git a/tools/setup_tools.sh b/tools/setup_tools.sh
index 2583de33..2fc31b9d 100755
--- a/tools/setup_tools.sh
+++ b/tools/setup_tools.sh
@@ -174,10 +174,10 @@ if [ "$OLD_OS" == "1" ]; then
ln -s -f ${MAPLE_ROOT}/tools/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f /usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
else
- ln -s -f /usr/bin/clang++ ${TOOL_BIN_PATH}/clang++
- ln -s -f /usr/bin/clang ${TOOL_BIN_PATH}/clang
- ln -s -f /usr/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
- ln -s -f /usr/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
+ ln -s -f /usr/lib/llvm-10/bin/clang++ ${TOOL_BIN_PATH}/clang++
+ ln -s -f /usr/lib/llvm-10/bin/clang ${TOOL_BIN_PATH}/clang
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ar ${TOOL_BIN_PATH}/llvm-ar
+ ln -s -f /usr/lib/llvm-10/bin/llvm-ranlib ${TOOL_BIN_PATH}/llvm-ranlib
ln -s -f ${MAPLE_ROOT}/tools/qemu/package/usr/bin/qemu-aarch64 ${TOOL_BIN_PATH}/qemu-aarch64
fi
ln -s -f ${MAPLE_ROOT}/tools/open64_prebuilt/x86/aarch64/bin/clangfe ${TOOL_BIN_PATH}/clangfe
```
@binaryfz @QunYeNB
新值
目前编译mplfe时 clang/llvm的头文件用的是系统安装的版本```LLVMINC = "${CLANG_PATH}/include"```。这样不同的系统由于不同的clang/llvm版本就会有差异,不利于维护。事实上mplfe用clang 10的头文件是编译失败的。
鉴于我们已经放了clang和llvm的文件在 ThirdParty/ 我们可以用它们,不过里面的文件似乎不完整。下面的patch可以作为改造的开始。
链接用到的clang/llvm库也需要放到 ThirdParty/
```
diff --git a/build/config.gni b/build/config.gni
index f6ce5124..
1
4
b
c
c9b1
100644
--- a/build/config.gni
+++ b/build/config.gni
@@ -1
9
,
9 +19,8 @@ if (OLD_OS == "1") {
} else {
CLANG_PATH = "
/usr"
}
-
LLVMI
N
C = "${CLANG_PATH}/include"
LLVMLIBDIR =
"${CLANG_PATH}/lib"
-CFE_SRC_DIR = "${MAPLE_ROOT}/../third-party/cfe-8.0.0.src"
+CFE_SR
C
_DIR = "${MA
P
LE_ROOT}/../ThirdParty/cfe-8.0.0.src"
CFE_SRC_PATH
= "${MAPLE_ROOT}/../ThirdParty/cfe-8.0.0.src"
ANDROID
_
GCC_PATH = "${MAPLE_ROOT}/tools/gcc"
diff --git a/src/mplfe/BUILD.gn b
/
src/mplfe/BUILD.gn
index e5eb1899..39778047 100644
--- a/src/mplfe/BUILD.gn
+++ b/src/mplfe/BUILD.gn
@@ -40,7 +40,8 @@ include_directories = [
"${MAPLE_ROOT}/third_party/bounds_checking_function/include",
"${MPLFE_ROOT}/ast_i
n
put/include",
"${MPLFE_ROOT}/ast_input/lib",
-
"${
LLVMINC}",
+
"
//../ThirdParty/cfe-8.0.0.src/include",
+
"
//../ThirdParty/llvm-8.0.0.src/include",
"
//../ThirdParty/cfe-8.0.0.src/tools",
]
```
@binaryfz @QunYeNB
BinaryFZ
关联了
方舟编译器/OpenArkCompiler Pull Request !540
BinaryFZ
通过
openarkcompiler/OpenArkCompiler Pull Request !540
将
任务状态
从
待办的
修改为
已完成
BinaryFZ
将
置顶等级
从
高
修改为
不置顶
展开全部操作日志
折叠全部操作日志
登录
后才可以发表评论
状态
已完成
待办的
进行中
已完成
已关闭
负责人
未设置
标签
未设置
标签管理
里程碑
未关联
未关联
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (27)
标签 (2)
master
lite_maplecg_assembler
merge_branch_20230823
merge_branch_20230608
lite_maplecg
update_llvm_15
merge_branch
wchen_merge169
dev_MapleFE
newir09
fredchow_ginlinepgo1
fredchow_lfovect1
wchen_merge174
fye_pgo_cglower
wchen_merge175
fredchow_lfounroll4
fredchow_funcdelete1
newir08
wchen_merge170
ahuang_m103
newir07
wchen_merge173
newir06
newir05
dev_MapleFE_v2
newir04
abstractir
v1.0.0
v0.2.1
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
参与者(1)
C++
1
https://gitee.com/openarkcompiler/OpenArkCompiler.git
git@gitee.com:openarkcompiler/OpenArkCompiler.git
openarkcompiler
OpenArkCompiler
OpenArkCompiler
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册