-
-
Notifications
You must be signed in to change notification settings - Fork 79
Groundwork for Skill Trees #990
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
Open
NocTempre
wants to merge
6
commits into
richardwilkes:master
Choose a base branch
from
NocTempre:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9b634fa
UseSkillTrees flag added.
NocTempre d9acfbc
Skill Tree Flag Turns off Default Skill Chaining Behavior
NocTempre 779eba5
Merge branch 'richardwilkes:master' into master
NocTempre c96db62
Merge branch 'richardwilkes:master' into master
NocTempre 3168201
Fix typos and added guards.
NocTempre 3015fa1
Merge branch 'richardwilkes:master' into master
NocTempre File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still not grasping why this is here. I build for Windows all the time and this is not needed. Specifically, the -s option disables symbols in the output and the -w option disables DWARF generation. Both of those should only be on the command line when building for a release. By setting them, you're making debugging harder for yourself.
If you're doing this because of some oddity in your particular setup (I believe you were the one having tons of difficulty compiling on Windows for some reason), it's unclear why this would help. It shouldn't have any effect with regards to that... and if it does, it just indicates there is something fundamentally wrong in your setup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hard to say, I'm very new to GO. I assumed the -w was a windows flag. I tried just -s and just -w and either and both was ok. Neither and it can't launch as an .exe for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran into this myself after updating one of my machines to Windows 11 (previously, I had only ever built on a Windows 10 or earlier machine). Unclear why that would make a difference, or if there is something else that changed compared to my older machine that is the actual issue and not Windows 11 itself.
Regardless, one of the recent changes was to the build.sh file to get around this anomaly.