[WIP][IntelliSense]Visual Studio & VS Code config #107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hdebinfo ] folders debuggind done on the debug folder
…ir" when pressing F bug
… crosshair" when pressing F bug" This reverts commit 9d5a83a.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Useful for those that develop in VS or VS Code... for building and debugging and IntelliSense
by default VS Code it is configured to build in ${workspaceRoot}/build and VS in ${workspaceRoot}/build/[x86-Debug]
It looks in the C:/MinGw/bin for gcc, g++ and gdb
Note: needs the CMake Tools for VS Code and Visual C++ tools for CMake
For VS: CMake Menu -> Cache - >Generate
-> Build copy [res] folder, SDL2.dll and SDL2_mixer.dll
Debug:
Note2: tested on Visual Studio Community 2017(15.7.5), on W10