LLAR Builder实现
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 4
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 22
Description
目录结构(MVP)
llar/
├── cmd/ # LLAR Cli模块
│ └── ...
├── internal/
│ ├── mvs/ # Go MVS选择算法
│ │ └── ...
│ ├── build/ # 构建模块
│ │ └── ...
│ ├── deps/ # 依赖模块
│ │ └── ...
│ └── ixgo/ # ixgo
│ └── ...
├── pkgs/ # FormulaApp工具类包
│ └── ...
└── formula.go # FormulaApp
模块划分
graph TD
A["依赖管理模块(deps)"]
B["LLAR Cli模块(cmd)"]
C[FormulaApp]
D[ixgo]
E["构建模块(build)"]
B --> E
E <--> A
A <--> C
C --> D
E --> D
D --> |加载|C
模块输入输出
依赖管理模块
功能:
- 增量添加依赖
- 通过Go MVS算法计算依赖有向图
- 解析
versions.json
输入:versions.json 的[]byte 或者文件路径
LLAR Cli模块
#17
FormulaApp
#21
ixgo运行模块
功能:
- 自动配置xgo项目(RegisterProject)
- 根据用户需求,找到需要的配方
- 与依赖管理模块互动
- 根据依赖管理模块,执行构建
依赖管理模块互动
graph TD
A["初始化:调用配方Main()"] --> B[执行配方onRequire回调]
B --> C[依赖管理模块]
C --> D[获取依赖有向图]
D --> E[获得Buildlist]
E --> F[根据Buildlist执行配方构建]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed layout for cmd, internal/mvs, internal/build, internal/deps, internal/ixgo, pkgs, and formula.go, along with issues #17 and #21. Trace the dependency-management and build flows in the diagrams. Done would require an agreed implementation scope for the LLAR Builder MVP and the listed module interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100