Closed elias-knodel closed 2 years ago
I don't know the exact workflow with TacO and VS. It worked for me like this but maybe a little more details for like how we can get a working dev environment would be useful.
I also would suggest changing the license... (look at #2)
are you sure thats the way to build it? because i get a lot of dlls in the release folder. compare to the program release by the author this build seems to generate too much crap. also have you test it on a clean windows machine? will it work or will need some other dependencies that comes with VS
edit: sorry not dlls. those are obj files
Is there any write-up showing how to build TacO? I'm not well-versed in msbuild
so might be doing something wrong. There are a bunch of issues I think I could work on but wanna make sure I can get the project built correctly before tackling them. :)
It's literally "load .sln into visual studio and press build"...
Description
This adds a readme with all needed information to set this project up for development, (Small extra change: extends the .gitignore because when you build it some folders get generated)
Related issue
Fixes #1
How can this be tested?
Set it up like its written in the README.md and look if it works without any complications.