Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
csdn_franckjun
Paddle
提交
cc070422
P
Paddle
项目概览
csdn_franckjun
/
Paddle
与 Fork 源项目一致
Fork自
PaddlePaddle / Paddle
通知
1
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
1
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
P
Paddle
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
1
Issue
1
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
cc070422
编写于
6月 29, 2017
作者:
W
wuyi05
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
update design doc
上级
60a65b5d
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
19 addition
and
9 deletion
+19
-9
doc/design/build_system/README.md
doc/design/build_system/README.md
+19
-9
未找到文件。
doc/design/build_system/README.md
浏览文件 @
cc070422
...
...
@@ -108,14 +108,14 @@ As above example CMakeLists.txt executes, each function invocation adds "nodes"
### Using Package Manager For Go
Building
g
o binaries and libraries need to satisfy their dependencies, generally
Building
G
o binaries and libraries need to satisfy their dependencies, generally
we can do
`go get ./...`
to download and compile all external dependencies. The
problems are:
1.
`go get`
will always get the latest code from
master branch, so when an external
project updated and deprecates something or made changes to their APIs, builds
may not pass. This is very different with what we already have in
`cmake/external`
which download a
specific version or commit id of the dependency.
1.
`go get`
will always get the latest code from
the default branch of the
remote repo, so changes of dependents might break the build. This is very
different with what we already have in
`cmake/external`
which download a
specific version or commit id of the dependency.
1.
Some locations can not access external dependencies through the internet, as mentioned
in https://github.com/PaddlePaddle/Paddle/issues/2605. Using package management
tools can package the dependencies as a "vendor" package, which can be mirrored
...
...
@@ -124,10 +124,20 @@ problems are:
#### Godep vs. Glide
Here's a brief comparison for current Go ecosystem: https://github.com/Masterminds/glide/wiki/Go-Package-Manager-Comparison. There are
also many complaints about
`Godep`
. A new "official" pakcage management tool has been
started: https://github.com/golang/dep to resolve such problems, but it's currently
at Alpha stage. So the best choice now is glide obviously.
As mentioned by @wangkuiyi,
[
Here
](
https://github.com/golang/go/wiki/PackageManagementTools
)
list dozens of Go package managers. We choose the tool using following principles:
-
Most "active" projects with more stars, more pull requests or commits
-
Commonly used project
Then we shall choose between the most popular tools: Godep and Glide.
Here's a brief comparison between Godep and Glide
: https://github.com/Masterminds/glide/wiki/Go-Package-Manager-Comparison. There are
also many complaints about using
`Godep`
. There's also a new "official" pakcage
management tool has been started at: https://github.com/golang/dep to resolve
such problems, but it's currently at Alpha stage. So the best choice now is
glide obviously.
#### Manage Go Packages
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录