Streamlining Build Process and File Structure #6
Conversation
This file contains hidden or 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
From "#include <GoldHEN/GoldHEN.h>" to just simply "#include <GoldHEN.h>"
Mention of the usage "make install".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds mention of
make allin the README which I'm not too worried about in my case.Created a folder named "GoldHEN" in
/includerather than at build sowhen built it'll automatically copy the file from the new folder within include.
Updated the source files to reflect the path changes and now when built you can simply
include like
#include <GoldHEN.h>rather than#include <GoldHEN/GoldHEN.h>.That should be all, not needed but easier for newcomers like myself when I started.