-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Tutorial on running EPIJudge on VS2019 #210
Comments
I got it working on VS 2019 with the command |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since I was struggling in solving my compilation issue with EPIJudge (C++) and now got it working on VS2019, I just post on details steps on how to run and compile EPIJudge C++ on VS2019. Besides the instruction on this package's README.md, these steps may be helpful for some of you:
1/ I assumed that you either have VS2019 (I used) or VS2017
2/ I assumed that you fork the EPIJudge to your git repository.
3/ I assumed that you git clone your forked repo to your local machine. In this step, I recommend for now to git clone EPIJudge to your desktop. I first tried to put it in another directory for the sack of file organization, however, it seems to give me an error when I tried to compile since the .cc file was too deep in the directory to find (or some other path error).
4/ Then do like what the author(s) instructed:
"
Here is an example recipe for generating a Visual Studio project (list of all CMake supported IDEs). After installing CMake, open your terminal, go to the epi_judge_cpp folder and run the following commands:
mkdir vs
cd vs
cmake -G "Visual Studio 15 2017" ..
"
5/ Then open VS2019>Open a project or solution> Wait > You should be able to see in your vs/ directory in VS2019's Solution Explorer tab (right tab) contains all the questions (not just the .cc but for each question it has "References", "External Dependencies, Source Files", and "CMakeLists.txt").
Note if you don't see Solution Explorer, go to View (on VS2019/2017)>Solution Explorer
6/ Say you want to test run parity.cc question. In your Solution Explorer, choose parity question>right click>Build> Wait> right-click again>Set as Startup Project>click on the green triangle on top of VS2019/2017 "Local Windows Debugger". This should run and give you a fail (since you did not have a solution for the question yet, just put in the solution from the solution directory, it should give you a pass).
Hope this helps!
The text was updated successfully, but these errors were encountered: