yonaskolb / yonaskolb/XcodeGen
codesigning executable embedded during buildPhase/copyFiles
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
Hi,
I'm using XCodeGen to generate an XCode project using an autotool project.
It is currently made of the following spec file:
name: VLC
options:
bundleIdPrefix: org.videolan.vlc
deploymentTarget:
iOS: 9.0
targets:
VLCAutomake:
type: ""
platform: ${VLC_PLATFORM}
legacy:
toolPath: /usr/bin/make
passSettings: true
attributes: $(ACTIONS)
workingDirectory: ${VLC_BUILD_DIR}
sources:
- path: "${VLC_SRC_DIR}/src"
excludes: "**/Makefile.in"
- path: "${VLC_SRC_DIR}/include"
excludes: "**/Makefile.in"
- path: "${VLC_SRC_DIR}/modules"
excludes: "**/Makefile.in"
vlccoreios:
type: "application"
platform: ${VLC_PLATFORM}
dependencies:
- target: VLCAutomake
info:
path: "vlccoreios/Info.plist"
sources:
- path: ${VLC_BUILD_DIR}/test/vlccoreios
type: file
optional: true
buildPhase:
copyFiles:
destination: executables
I'm basically building most of the targets from the automake target, and then use XCode to package them into an iOS or tvOS application.
However, the executable used in the vlccoreios target is not code signed and it doesn't seem that there is a way to sign it within the buildPhase, so it must be checked within the project each time it is generated again.
Is it possible to add the sign: true like for dependencies here?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VLCAutomake dependency and the vlccoreios source entry in the provided spec, focusing on the buildPhase/copyFiles configuration and generated Xcode project. Compare the generated project with the requested sign behavior and verify that the embedded executable is signed after regeneration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100