Skip to content
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

Move tools to site_scons/site_tools, which is the canonical scons tools directory. Pass env["toolpath"] down the tool chain in godotcpp.py. #1645

Closed
wants to merge 1 commit into from

Conversation

Ivorforce
Copy link
Contributor

We should strive to adapt tool standards.

With this change, passing toolpath is no longer required in normal cases. Read more here: https://scons.org/doc/production/HTML/scons-user/ch07s04.html#id1354

@Ivorforce Ivorforce requested a review from a team as a code owner November 19, 2024 23:21
@Ivorforce
Copy link
Contributor Author

Ivorforce commented Nov 19, 2024

Ok, I also solved one issue where toolpath wasn't passed down as is normally expected through godotcpp.py and SConstruct.

I hope the new implementation is now more idiomatic. One reason I changed it is because I was running into issues trying to use custom tool and working directories, and the current implementation made it impossible because of path assumptions.

@Ivorforce Ivorforce force-pushed the site_scons branch 7 times, most recently from 447d663 to 55cc681 Compare November 20, 2024 00:57
@Ivorforce Ivorforce changed the title Move tools to site_scons/site_tools, which is the canonical scons tools directory. Move tools to site_scons/site_tools, which is the canonical scons tools directory. Pass env["toolpath"] down the tool chain in godotcpp.py. Nov 20, 2024
…ls directory. Pass toolpath down the tool chain in godotcpp.py.
@dsnopek
Copy link
Collaborator

dsnopek commented Nov 20, 2024

I don't know about this.

The site_scons/ directory feels more like a thing for a full project using scons (which in this case would be the GDExtension project that uses godot-cpp) rather than godot-cpp itself, which is more of a "component" used by other projects.

Also, setting a custom toolpath is fairly normal thing to do. I don't see our use of that feature being particularly hacky or anything.

One reason I changed it is because I was running into issues trying to use custom tool and working directories, and the current implementation made it impossible because of path assumptions.

Can you explain in more detail the problem you were having? Perhaps there is a simpler solution.

@Ivorforce
Copy link
Contributor Author

Can you explain in more detail the problem you were having? Perhaps there is a simpler solution.

There's a bit of a background to this PR. I opened #1646 to let you in on my thoughts.

@Ivorforce
Copy link
Contributor Author

Closing as per GDExtension meeting discussion. I will open small PRs to address specific issues brought up in #1646.

@Ivorforce Ivorforce closed this Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants