yonaskolb / yonaskolb/XcodeGen

Follow Xcode to allow copying without requiring embed=true

Open
#1,206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
8.8k
Forks
908
Avg merge
17d 14h
Merged PRs (30d)
2

Description

Can you please drop the requirement that embed should be set to true to allow for copying. This is not a requirement of Xcode. Indeed in my case, it will not work if I embed a Framework, but only if I copy it (without embedding it) so I was hoping for the following to work in xcodegen so as to be consistent with how my current xcode project works (please see screenshot below):

name: demo
options:
  bundleIdPrefix: org.me
settings:
  CODE_SIGN_IDENTITY: "-"
  DEVELOPMENT_TEAM: ""
  GCC_OPTIMIZATION_LEVEL: 0
  GCC_NO_COMMON_BLOCKS: No
  HEADER_SEARCH_PATHS:
    - $(PROJECT_HEADERS)
  INFOPLIST_FILE: $(SRCROOT)/../../../Info.plist
  LIBRARY_SEARCH_PATHS: $(PROJECT_LIBS)
  OTHER_LDFLAGS:
    - $(PROJECT_LDFLAGS)
  PRODUCT_NAME: $(TARGET_NAME)
configFiles:
  Debug: project.xcconfig
  Release: project.xcconfig

targets:
  py:
    type: bundle
    platform: macOS
    sources:
      - ../../py.c
    dependencies:
      - sdk: CoreFoundation.framework
      - framework: ../build/lib/Python.framework
        embed: false
        copy: 
          destination: resources
    settings:
      MACOSX_DEPLOYMENT_TARGET: "10.13"
screenshot

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with XcodeGen's dependency handling for the shown target and the framework dependency fields. Verify how embed: false interacts with copy.destination: resources; done means the YAML example generates an Xcode project that copies the framework without requiring embedding, with appropriate coverage added if an existing test area is found.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.