Carthage/Carthage

Feature request: make copy-frameworks optionally not strip architectures

Open

#1,810 opened on Mar 3, 2017

View on GitHub
 (4 comments) (13 reactions) (0 assignees)Swift (15,179 stars) (1,544 forks)batch import
enhancementhelp wanted

Description

In any project with several Carthage dependencies, calling /usr/local/bin/carthage copy-frameworks starts becoming a very large part of the compilation time. AFAIK most of that time is due to stripping architectures.

However, I just realized that if we made that optional, we could make it only do that when archiving for submission, and in that way make iteration times much lower.

Contributor guide

Tech stack
swiftshell
Domain
toolingbuild system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of Carthage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the copy frameworks script in Carthage (likely in the 'Source/carthage' directory). Look for the architecture stripping logic, possibly in a function named 'stripArchitectures'. Consider adding a command line flag like ' no strip architectures' that conditionally skips that step. Review the existing code and any related issues or PRs for context.