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

Making godot-cpp scons more idiomatic #1646

Open
Ivorforce opened this issue Nov 21, 2024 · 0 comments
Open

Making godot-cpp scons more idiomatic #1646

Ivorforce opened this issue Nov 21, 2024 · 0 comments

Comments

@Ivorforce
Copy link
Contributor

Ivorforce commented Nov 21, 2024

Godot version

4.4 (master)

godot-cpp version

4.4 (c20a84e)

System information

macOS

Issue description

Can you explain in more detail the problem you were having?

I've been having a bit of friction with how godot-cpp and its dependents (i.e. our recommended setup godot-cpp-template) interact. Specifically, I've been running into several problems trying to get a structure better structure for my SConstruct (and subsequently, contributing the changes to godot-cpp-template). It's a WIP.

I've found the SCons documentation not to be exhaustive, but I've been talking to SCons maintainers on Discord, who have been incredibly helpful in filling my missing pieces of knowledge.

Here's my latest gripe.

Custom options

When a godot-cpp dependent defines a new config option, godot-cpp complains about the new variable through these lines of code:

godot-cpp/SConstruct

Lines 37 to 41 in c20a84e

unknown = opts.UnknownVariables()
if unknown:
print("WARNING: Unknown SCons variables were passed and will be ignored:")
for item in unknown.items():
print(" " + item[0] + "=" + item[1])

This is because arguments persist in ARGUMENTS, and godot-cpp finds and does not recognize them. This is confusing to the CLI user. We could remove the argument check, but then it would also be gone from godot-cpp's standalone use. I think using its SConstruct for both standalone and dependants is a bit of a split of two different interests, and may lead to more issues like this. Not to mention, it could be worth it to work toward better compartmentalization to eventually support dependency chains linking against each other.

Modularizing

SCons maintainers suggested not to use SConscript. SConscript is intented for sub-projects, rather than for dependencies (though arguably, godot-cpp is both). In their suggestion, godot-cppp's SConstruct would be used only to build it standalone, while its dependants would have their own SConstruct and call its tools explicitly. I do like this idea, because it favors modularity. Trying to implement it, however, I ran into several issues:

Depending on your viewpoint, you could interpret this as either

  • "godot-cpp makes too many assumptions about pwd, and should more agnostic, or state / adopt its assumptions more explicitly."
  • "just use SConscript, that avoids all these problems."

Anyway, without making any judgement calls just yet, I opted to experiment more to see if godot-cpp could actually be compartmentalized into a toolchain. But I thought #1645 would be relatively uncontentional, since it merely adapts what is the tooling standard of SCons (I should note here that the authors were specifically confused as to why godot-cpp's tools were not in site_tools but rather elsewhere).

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

No branches or pull requests

1 participant