Carthage/Carthage

Explain how schemes are found in subprojects vs. workspaces

Open

#108 创建于 2014年11月19日

在 GitHub 查看
 (14 评论) (0 反应) (0 负责人)Swift (15,179 star) (1,544 fork)batch import
buildenhancementhelp wantedquestion

描述

This feels like a tricky one. Currently, Quick already builds Nimble. But if you want to manage Nimble separately (which you probably do), there's no way to specify that you should use the version of Nimble.framework from the Nimble repository. Carthage builds Nimble first (I'm assuming because of alphabetical sorting?) then builds Quick, which clobbers the version built by Nimble.

Not sure if this should be opened with Quick as well (their installation instructions say to install them separately). But an "easy" (if heavy-handed) way to resolve this might be to install dependencies in the order that they are listed in the Cartfile.

/cc @modocache

贡献者指南

技术栈
swiftshell
领域
toolingbuild system
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
familiarity with Carthagebasic understanding of dependency managers
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the order in which Carthage builds dependencies. The issue mentions that dependencies are built alphabetically, causing Nimble to be built before Quick and then overwritten. Look at the Carthage source code for dependency resolution logic, particularly in the `build` or `resolve` commands. Search for alphabetical sorting and consider how to change it to respect Cartfile order. Also check the comments for any proposed solutions or further details.