-
Couldn't load subscription status.
- Fork 1
ucsd-cse-125-spring-2019/cse125-sp19-group3
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
- - - - - - - - Setting up Visual Studio Environment: 1.) Open the solution file located in 'rendering -> CSE125G3.sln' 2.) From the solution explorer right click on the solution then... a.) Provide command line arguments i.) Select properties -> Debugging -> command arguments --> For Server: server --> For Client: client --> To run a Client and Server on same process: multi b.) Ignore specific warnings i.) Select properties -> C/C++ -> Preprocessor ii.) Add this line to the end of 'Preprocessor Definitions' (semicolon included) --> ;_CRT_SECURE_NO_WARNINGS 3.) Install all the required packages a.) Tools -> NuGet package manager -> Manage Nuget Packages for solution *** NOTE: You might get notificaton 'install missing packages', if so do it and it should install them automatically. b.) Install the following... -> glm -> nupengl.core -> nupengl.core.redist -> spdlog.native -> spdlog-native -> nlohmann.json 4.) Try to compile and run. If an error shows up saying "assimp-vc140-mt.dll not found", do the following: Copy the file assimp-vc140-mt.dll -> from rendering/Assimp/lib/ -> to rendering/x64/Debug/ *** Note: If you're using a different version of VS (non-2017) see below! - - - - - - - - Setting up the Visual Studio Environment (non-2017): -> Be sure to also follow the setup for setting up VS for the first time. -> The lab machines use Visual Studio 2017. If you have a different version of VS you'll need to install a few things. -> All of the following can be installed using the Visual Studio Installer (it will modify the existing copy of VS). 1.) Windows SDK: 10.0.16299 2.) Platform toolset: Visual Studio 2017 build tools v=141 3.) Once installed you can right click the project -> properties -> General. Make sure SDK & platform toolset are correct. - - - - - - - - Sending Requests to Server without running the client: -> You can test the server connection without running the client by using the *nux commands that'll make requests to the server 1.) After running the server input 'nc <host> <port>' into the terminal to make a request to the server. --> You can also run 'nc -C <host> <port>' and it will allow you to write input to stdin and send that to the server. 2.) An alternative would be to use 'curl -v <host>:<port>' --> '-v' for verbose mode, shows the GET request and how the server handles it. --> Makes a simple GET request to the server.
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Packages 0
No packages published