-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beginner Question: I can't find any of the .exe files? #6
Comments
Open the project in visual studio and click Build -> Rebuild. If all is built successfully you will see the KinectServer.exe file in the path "\ProCamCalibration\KinectServer\bin\Debug" and similarly for other .exe files. |
Thank you! Would you know how I can test out the mapping samples? Clicking on the .exe does not work. |
I am still trying to get it to run. Try to follow the instructions in README.md |
Yea I wasn’t too sure how too sure how to pass the xml as an argument. Do I open command prompt and put both file names in there? From: Chi-Jui Wu [mailto:notifications@github.com] I am still trying to get it to run. Try to follow the instructions in README.md — |
If, like me, building this project is your first foray into visual studio and NuGet and you see errors like this: Error This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\SharpDX.2.6.3\build\SharpDX.targets. Try adding http://www.nuget.org/api/v2/ as a source in your NuGet package manager settings source list. I was unable to build due to NuGet failing to find the SharpDX.2.6.3 package at all in the NuGet api v3 source that is configured by default in visual studio 2015. |
Interesting. I just pulled down a fresh .zip file and didn't see this behavior. |
This is my first time really building something on Github. How do I build this repository to create the .exe files.
When I download the repository I don't see any .exe files.
The text was updated successfully, but these errors were encountered: