Don't hard code header locations, use <SDL2/SDL.h> #7
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.
This gives us the flexibility of finding headers wherever they
maybe installed. Currently I'm creating symlinks to the homebrew
build of libSDL2 /usr/local/include and /usr/local/lib.
Description
To be able to build against headers installed EITHER in /usr/include OR /usr/local/{include,lib}, simply reference <SDL2/SDL_*.h>. On Linux, this means the headers will be found in /usr/include if they SDL development package is installed via apt (on Debian), or in /usr/local/include (suitably symlinked) when using some alternative package manager such as Homebrew.
Detailed Design
No new APIs, just some header file changes.
Documentation
How has the new feature been documented?
Have the relevant portions of the guides in the Documentation folder been updated in addition to symbol-level documentation?
Testing
*How is the new feature tested?
Tested building on WSL Debian distribution.
Performance
N/A
Source Impact
It should simplify things.
Checklist