ChilliCream / ChilliCream/graphql-platform
Build target error with absolute build output paths
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Product
Strawberry Shake
Version
13.9.6
Link to minimal reproduction
https://github.com/ir-dev/bug-repro_strawberry-shake_absolute-build-output-paths
Steps to reproduce
Build the project
What is expected?
Build should be successful with the absolute build output paths being recognised correctly
What is actually happening?
Build fails when using artifacts output layout with defaults as described in https://learn.microsoft.com/en-us/dotnet/core/sdk/artifacts-output. That means a Directory.Build.props file with UseArtifactsOutput property set to true will use actually legitimate absolute paths set as common build project paths which StrawberryShake.Server.targets expects to be relative.
If a relative path is set for ArtifactsPath property which otherwise uses this default $(MSBuildThisFileDirectory)artifacts then it would work again.
Relevant log output
strawberryshake.server\13.9.6\build\StrawberryShake.Server.targets(85,5): 'C:\Users\johndoe\source\repos\bug-repro_strawberry-shake_absolute-build-output-paths\Demo\C:\Users\johndoe\source\repos\bug-repro_strawberry-shake_absolute
-build-output-paths\artifacts\obj\Demo\debug\berry'
Additional context
No response
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 minimal reproduction and inspect StrawberryShake.Server.targets at line 85, then compare its path handling with the Directory.Build.props settings described in the issue. Build the reproduction using the artifacts output layout and verify that the build succeeds when absolute output paths are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100