yonaskolb/XcodeGen

[BUG] Optional source path doesn't work if executing xcodegen from outer directory

Open

#1453 opened on Feb 22, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Swift (8,431 stars) (881 forks)batch import
bughelp wanted

Description

Given a project config:

name: OptionalSourcePath

targets:
  OptionalSourcePath:
    type: application
    platform: iOS
    deploymentTarget: "16.0"
    sources:
      - path: "First"
      - path: "Second"
        optional: true

and a directory structure of:

❯ tree dir
dir
├── First
├── Second
└── project.yml

3 directories, 1 file

calling xcodegen from within dir:

cd dir
xcodegen -s project.yml

generates a correct Xcode project.

However, calling xcodegen from outside of dir:

❯ basename $PWD
Downloads
❯ ls dir
First  project.yml  Second
❯ xcodegen -s dir/project.yml

Generates an Xcode project where the "Second" dir is missing from file tree: missing

❯ xcodegen --version
Version: 2.39.1

Contributor guide

Tech stack
swift
Domain
clideveloper experiencetooling
Issue type
bug
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Swift programmingXcodeGen codebase structurefile path handling in Swift
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate how XcodeGen resolves source paths when the current working directory differs from the project directory. Focus on the SpecParsing or ProjectGenerator files where source paths are processed. The optional attribute may affect path resolution. Ensure relative paths are resolved relative to the project file location, not the current working directory.