Support custom compiler arguments in dotnet build

[monxa]

Proposal to Enable Custom Compiler Arguments in dotnet build

The What

This pull request allows users to pass additional compiler arguments to the dotnet build process to enhance flexibility and potentially reduce build times.

This implementation is based on the proposal by @paulloz. It emerged after the rejection of my previous attempt to address build times, which rightly so got rejected after careful review by @raulsntos (see original proposal).

In Detail

Changes to Project Settings

• Added new settings:

dotnet/build/custom_compiler_arguments
dotnet/build/custom_publish_arguments

Modifications to Build Process

• BuildInfo.cs: Added a new property CustomArguments.
• BuildManager.cs: Introduced a new method AddCustomBuildArguments(BuildInfo buildInfo, bool publish) to parse the custom arguments from ProjectSettings.
• Applied this method in CreateBuildInfo and CreatePublishBuildInfo.
• BuildSystem/BuildArguments: Integrated the custom arguments from BuildInfo.

Demonstration

The custom arguments are hidden by default and can be found under "Advanced settings" for Mono builds:

Both Build and Rebuild processes respect the custom compiler arguments:

• Bugsquad edit, closes: Dotnet: Allow passing custom build arguments godot-proposals#10028

[lfshr]

One great addition here would be the ability to provide extra arguments in an export preset. It would help replace GODOT_SERVER above and allow people to compile code in their dedicated servers that should not be present in the clients.

[monxa]

One great addition here would be the ability to provide extra arguments in an export preset. It would help replace GODOT_SERVER above and allow people to compile code in their dedicated servers that should not be present in the clients.

Oh yes. The current state of this draft only differentiates between publish (export) and in-editor. I haven't considered export presets because

• that's not my main use for this draft
• the exporter might change

These are not strong arguments and if I find time and feel charity-ish, I might find a solution for export template options. In the meantime, if anyone wants to expand on this draft, please let me know!

One idea I have for working around such a user-friendly solution tho:

• You could write an ExporterPlugin
  • Cache and overwriting the ProjectSetting variables on _export_begin
  • Restore them on _export_end.

I have done something similar for the godot-git-plugin to avoid it being exported (godotengine/godot-git-plugin#77 (comment)).