Quantcast
Channel: Questions in topic: "build"
Viewing all articles
Browse latest Browse all 4084

Possible to make build output clean?

$
0
0
When I build my project in Unity, the output is like this: Game.exe Game_Data Game_Data\Managed\Lots of dll files Game_Data\Mono <-- A folder just for mono, really? Game_Data\Plugins\More dll files Game_Data\Resources\ 'unity default resource' + 'unity_builtin_extra' Game_Data\level# (lots of these files cluttering the directory) Game_Data\mainData Game_Data\PlayerConnectionConfigFile Game_Data\resources.assets Game_Data\sharedassets#.assets (lots of these) Is it really necessary to have all this? For example, is there a way I can combine all the 'level#' files into a single filed called 'levels', and combine all the asset files into a single file called 'assets'? Also when I'm working on c# .net projects, I usually embed the dependencies into the executable so that when I distribute the project the end-user doesn't have a folder cluttered with dll's, is it possible to do something like that with the Managed/Mono/Plugins dependency folders? Is it possible to get access to whatever method tells my project where to look for Mono for example?

Viewing all articles
Browse latest Browse all 4084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>