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 (15,179 stars) (1,544 forks)batch import
bughelp wanted

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

Tech stack
swift
Domain
build systemtooling
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.
under 1 hour
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 Swift knowledgeunderstanding of Carthage's directory structurefamiliarity with file I/O
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue is that when only binary dependencies are used, the 'Carthage/Build/' directory is not created, causing a file write error. To fix, ensure the directory exists before writing version files, likely in the code that handles binary dependencies. Look in 'Source/Carthage/' for where version files are written (e.g., 'writeVersionFile' or similar). Ensure that a 'mkdir' call is made for the build directory when it does not exist. Check for any existing directory creation logic for other dependency types and apply it to binary dependencies as well.