Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Building in Visual Studio
See original GitHub issueFrom @terrajobst on Mar 26
On a clean machine, opening the solution file and building in VS fails as the Tools folder doesn’t exist. Just running init-tools.cmd doesn’t fix it either as it now fails with malformed AssemblyInfo.cs files.
I’m still trying to get build working from the command line (where I get mostly actionable error messages, like Install CMake) this feels like the sort of thing that discourages contributors quickly. Ideally, you should be able to clone the repo, open the solution in VS, and building immediately.
Thoughts?
Issue Analytics
- State:
- Created 5 years ago
- Comments:29 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Just a shot a in the dark - but can you try a folder without a space in it? We’ve had issues with having spaces in the repo path before:
C:\My Data.net sample code\MachineLearning\try
C:\MyDataSampleCode\MachineLearning\Yeah, we probably have some build logic that isn’t quoting the path correctly. CMake does support spaces in the path name, if you do it right.
https://github.com/dotnet/machinelearning/pull/2925 is an example of fixing such a build logic error.