In our product, we integrate build via xcode with another build system. To reuse existing infrastructure, we generate both the spec yaml file and other yamls this spec file includes.
This means, that we in effect have 3 directory structures we work with:
1) spec file and its relative includes (defined via --spec)
2) source files defined via (--project-root)
3) directory into which project files are generated (--project)
However it seems that this behavior has been broken, probably by https://github.com/yonaskolb/XcodeGen/pull/1262/files
as it seems that in the newest xcodegen the relative includes of from within spec .yaml are relative to --project-root.
The old behavior was significantly more flexible. Would it be possible to revert to the previous behavior, either by default or via a command line switch? If I implement this as a pull request, would there be an interest to merge this to the mainline?
In our product, we integrate build via xcode with another build system. To reuse existing infrastructure, we generate both the spec yaml file and other yamls this spec file includes.
This means, that we in effect have 3 directory structures we work with: 1) spec file and its relative includes (defined via --spec) 2) source files defined via (--project-root) 3) directory into which project files are generated (--project)
However it seems that this behavior has been broken, probably by https://github.com/yonaskolb/XcodeGen/pull/1262/files as it seems that in the newest xcodegen the relative includes of from within spec .yaml are relative to --project-root.
The old behavior was significantly more flexible. Would it be possible to revert to the previous behavior, either by default or via a command line switch? If I implement this as a pull request, would there be an interest to merge this to the mainline?