Carthage/Carthage

If you have *only* a binary dependency, then `Carthage/Build/` doesn't get created.

Open

#2,304 opened on Jan 2, 2018

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Swift (1,544 forks)batch import
bughelp wanted

Repository metrics

Stars
 (15,179 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

  • carthage version: 0.27.0

  • xcodebuild -version: Xcode 9.2 Build version 9C40b

  • Are you using --no-build? no

  • Are you using --no-use-binaries? no

  • Are you using --use-submodules? no

  • Are you using --cache-builds? no

Cartfile binary "https://raw.githubusercontent.com/rogerzhang/carthageDemo/ff/mobile-ios-SDK.json" ~> 1.3.0

binary "https://raw.githubusercontent.com/rogerzhang/carthageDemo/ff/mobile-ios-SDK.json" ~> 1.3.0

Carthage Output

lmxmn166:test jacob.jiang$ carthage update *** Downloading binary-only framework mobile-ios-SDK at "https://raw.githubusercontent.com/rogerzhang/carthageDemo/ff/mobile-ios-SDK.json" Failed to write to /Users/jacob.jiang/test/Carthage/Build/.mobile-ios-SDK.version: Error Domain=NSCocoaErrorDomain Code=4 "The folder “.mobile-ios-SDK.version” doesn’t exist." UserInfo={NSFilePath=/Users/jacob.jiang/test/Carthage/Build/.mobile-ios-SDK.version, NSUserStringVariant=Folder, NSUnderlyingError=0x7ffe2bf1b0e0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

Contributor guide

Research direction
Ensure the Carthage/Build/ directory is created when only binary dependencies are present. Investigate where the directory creation logic is implemented and add a check to create it if missing.
Tech stack
swift
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSwiftXcode
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75