Open crazydef opened 1 month ago
Possibly related, I also see these warnings from xcode when building:
2024-07-31 10:07:33.155 xcodebuild[99013:2054129] warning: The file reference for "A.xcodeproj" is a member of multiple groups ("Projects" and "Projects"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path.
2024-07-31 10:07:33.155 xcodebuild[99013:2054129] warning: The file reference for "B.xcodeproj" is a member of multiple groups ("Projects" and "Projects"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path.
2024-07-31 10:07:33.170 xcodebuild[99013:2054129] warning: The file reference for "A.xcodeproj" is a member of multiple groups ("Projects" and "Projects"); this indicates a malformed project. Only the membership in one of the groups will be preserved (but membership in targets will be unaffected). If you want a reference to the same file in more than one group, please add another reference to the same path.
What seems to be the problem? I have a workspace with multiple shared library projects and multiple applications.
As you would expect, each project has multiple configurations:
The output from each project has the configuration as part of the name:
The applications use
dependson
andlinks
to setup build dependencies and linker inputs.However, when using links as follows:
Xcodebuild only ever attempts to use the Debug build of a library, regardless of the configuration actually being built.
To work around this, it is necessary to specify the entire library name in the links setting:
The documentation for links says:
For Windows (vs2022) and Linux (gmake2) the above appears to be correct. However, this is not the case on MacOS.
Related to this, it appears build dependencies are also not set correctly on any platform, (I must use both
links
anddepends
) but that could be a consequence of needing to specify the full library name.What did you expect to happen? I expected MacOS to work the same as other platforms.
How can we reproduce this? Test.zip
Unzip the attached, and run the following commands to reproduce the issue:
What version of Premake are you using? 5.0.0-dev