Configure output folder of assemblies for Unity
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
One of the examples when this is needed is when using Paket with Unity3D projects. Unity is picky about where dlls can be located (they have to be anywhere inside Assets/ folder in the project root as far as I understand) and as such there is no automated way to place them where they should be.
There is Paket.Unity3D (https://github.com/wooga/Paket.Unity3D), which attempts to solve the problem but it doesn't seem to be actively maintained (judging by commit history and build status) and besides, running it results in dlls being stored in 2 places (as can be seen on http://wooga.github.io/Paket.Unity3D/tutorial.html under "Installing the dependency" section).
Any chance above mentioned use case will make you reconsider your opinion on the subject?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no Paket files or tests. Start by reviewing Paket's existing assembly output behavior and the linked Paket.Unity3D example, then determine how a configurable destination inside Unity's Assets/ folder should work. Done means the requested configuration is defined and duplicate assembly copies are avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- unity
- Domain
- build-system, game-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100