Allow defining project dependencies.
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 466
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Hello.
In my company's projects we now have a few native libraries that are wrapped by CppSharp, and that requires dedicated projects to setup the bindings. We'd like to add dependencies to those projects so they build order is correct.
This is possible with the ProjectDependencies section:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "NativeWrapper", "NativeWrapper.vcxproj", "{WRAPPER-GUID}"
ProjectSection(ProjectDependencies) = postProject
{BINDING-GENERATOR-GUID} = {BINDING-GENERATOR-GUID}
EndProjectSection
EndProject
Currently it seems it is not possible to generate this information with SlnGen.
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 by tracing how SlnGen emits project entries in generated .sln files. Use the ProjectDependencies section in the issue as the expected output, then verify that declared wrapper and binding-generator dependencies produce the correct build order in a generated solution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100