2016-10-17 08:50:25 +02:00
|
|
|
#!/usr/bin/env python
|
|
|
|
|
2020-03-30 08:28:32 +02:00
|
|
|
Import("env")
|
2014-02-10 02:10:30 +01:00
|
|
|
|
2018-09-28 13:29:52 +02:00
|
|
|
import os
|
2023-11-21 22:26:07 +01:00
|
|
|
from pathlib import Path
|
2018-03-17 23:23:55 +01:00
|
|
|
from platform_methods import run_in_subprocess
|
|
|
|
import platform_windows_builders
|
2014-02-10 02:10:30 +01:00
|
|
|
|
Add new VS proj generation logic that supports any platform that wants to opt in
Custom Visual Studio project generation logic that supports any platform that has a msvs.py
script, so Visual Studio can be used to run scons for any platform, with the right defines per target.
Invoked with `scons vsproj=yes`
To generate build configuration files for all platforms+targets+arch combinations, users should call
```
scons vsproj=yes platform=XXX target=YYY [other build flags]
```
for each combination of platform+target[+arch]. This will generate the relevant vs project files but
skip the build process, so that project files can be quickly generated without waiting for a command line
build. This lets project files be quickly generated even if there are build errors.
All possible combinations of platform+target are created in the solution file by default, but they
won't do anything until each one is set up with a scons vsproj=yes command for the respective platform
in the appropriate command line. This lets users only generate the combinations they need, and VS
won't have to parse settings for other combos.
Only platforms that opt in to vs proj generation by having a msvs.py file in the platform folder are included.
Platforms with a msvs.py file will be added to the solution, but only the current active platform+target+arch
will have a build configuration generated, because we only know what the right defines/includes/flags/etc are
on the active build target currently being processed by scons.
Platforms that don't support an editor target will have a dummy editor target that won't do anything on build,
but will have the files and configuration for the windows editor target.
To generate AND build from the command line, run
```
scons vsproj=yes vsproj_gen_only=no
```
2023-11-14 13:39:44 +01:00
|
|
|
sources = []
|
|
|
|
|
2016-10-30 18:57:40 +01:00
|
|
|
common_win = [
|
2019-02-12 15:43:54 +01:00
|
|
|
"godot_windows.cpp",
|
|
|
|
"crash_handler_windows.cpp",
|
2016-10-30 18:44:57 +01:00
|
|
|
"os_windows.cpp",
|
2020-03-09 16:56:48 +01:00
|
|
|
"display_server_windows.cpp",
|
2019-02-12 15:43:54 +01:00
|
|
|
"key_mapping_windows.cpp",
|
|
|
|
"joypad_windows.cpp",
|
2021-11-04 13:33:37 +01:00
|
|
|
"tts_windows.cpp",
|
2019-07-12 15:18:30 +02:00
|
|
|
"windows_terminal_logger.cpp",
|
2021-11-12 13:49:49 +01:00
|
|
|
"gl_manager_windows_native.cpp",
|
|
|
|
"gl_manager_windows_angle.cpp",
|
|
|
|
"wgl_detect_version.cpp",
|
2023-12-19 18:57:56 +01:00
|
|
|
"rendering_context_driver_vulkan_windows.cpp",
|
2014-02-10 02:10:30 +01:00
|
|
|
]
|
|
|
|
|
2022-10-14 12:18:25 +02:00
|
|
|
common_win_wrap = [
|
|
|
|
"console_wrapper_windows.cpp",
|
|
|
|
]
|
|
|
|
|
2023-11-21 22:26:07 +01:00
|
|
|
|
|
|
|
def arrange_program_clean(prog):
|
|
|
|
"""
|
|
|
|
Given an SCons program, arrange for output files SCons doesn't know about
|
|
|
|
to be cleaned when SCons is called with --clean
|
|
|
|
"""
|
|
|
|
extensions_to_clean = [".ilk", ".exp", ".pdb", ".lib"]
|
|
|
|
for program in prog:
|
|
|
|
executable_stem = Path(program.name).stem
|
|
|
|
extra_files_to_clean = [f"#bin/{executable_stem}{extension}" for extension in extensions_to_clean]
|
|
|
|
Clean(prog, extra_files_to_clean)
|
|
|
|
|
|
|
|
|
2020-03-30 08:28:32 +02:00
|
|
|
res_file = "godot_res.rc"
|
2018-09-01 05:53:18 +02:00
|
|
|
res_target = "godot_res" + env["OBJSUFFIX"]
|
|
|
|
res_obj = env.RES(res_target, res_file)
|
2015-11-08 23:53:58 +01:00
|
|
|
|
Add new VS proj generation logic that supports any platform that wants to opt in
Custom Visual Studio project generation logic that supports any platform that has a msvs.py
script, so Visual Studio can be used to run scons for any platform, with the right defines per target.
Invoked with `scons vsproj=yes`
To generate build configuration files for all platforms+targets+arch combinations, users should call
```
scons vsproj=yes platform=XXX target=YYY [other build flags]
```
for each combination of platform+target[+arch]. This will generate the relevant vs project files but
skip the build process, so that project files can be quickly generated without waiting for a command line
build. This lets project files be quickly generated even if there are build errors.
All possible combinations of platform+target are created in the solution file by default, but they
won't do anything until each one is set up with a scons vsproj=yes command for the respective platform
in the appropriate command line. This lets users only generate the combinations they need, and VS
won't have to parse settings for other combos.
Only platforms that opt in to vs proj generation by having a msvs.py file in the platform folder are included.
Platforms with a msvs.py file will be added to the solution, but only the current active platform+target+arch
will have a build configuration generated, because we only know what the right defines/includes/flags/etc are
on the active build target currently being processed by scons.
Platforms that don't support an editor target will have a dummy editor target that won't do anything on build,
but will have the files and configuration for the windows editor target.
To generate AND build from the command line, run
```
scons vsproj=yes vsproj_gen_only=no
```
2023-11-14 13:39:44 +01:00
|
|
|
env.add_source_files(sources, common_win)
|
|
|
|
sources += res_obj
|
2023-01-09 16:56:16 +01:00
|
|
|
|
|
|
|
prog = env.add_program("#bin/godot", sources, PROGSUFFIX=env["PROGSUFFIX"])
|
2023-11-21 22:26:07 +01:00
|
|
|
arrange_program_clean(prog)
|
2015-05-03 23:18:56 +02:00
|
|
|
|
2022-10-14 12:18:25 +02:00
|
|
|
# Build console wrapper app.
|
|
|
|
if env["windows_subsystem"] == "gui":
|
|
|
|
env_wrap = env.Clone()
|
|
|
|
res_wrap_file = "godot_res_wrap.rc"
|
|
|
|
res_wrap_target = "godot_res_wrap" + env["OBJSUFFIX"]
|
|
|
|
res_wrap_obj = env_wrap.RES(res_wrap_target, res_wrap_file)
|
|
|
|
|
|
|
|
if env.msvc:
|
|
|
|
env_wrap.Append(LINKFLAGS=["/SUBSYSTEM:CONSOLE"])
|
|
|
|
env_wrap.Append(LINKFLAGS=["version.lib"])
|
|
|
|
else:
|
|
|
|
env_wrap.Append(LINKFLAGS=["-Wl,--subsystem,console"])
|
|
|
|
env_wrap.Append(LIBS=["version"])
|
|
|
|
|
|
|
|
prog_wrap = env_wrap.add_program("#bin/godot", common_win_wrap + res_wrap_obj, PROGSUFFIX=env["PROGSUFFIX_WRAP"])
|
2023-11-21 22:26:07 +01:00
|
|
|
arrange_program_clean(prog_wrap)
|
2023-08-23 08:54:06 +02:00
|
|
|
env_wrap.Depends(prog_wrap, prog)
|
Add new VS proj generation logic that supports any platform that wants to opt in
Custom Visual Studio project generation logic that supports any platform that has a msvs.py
script, so Visual Studio can be used to run scons for any platform, with the right defines per target.
Invoked with `scons vsproj=yes`
To generate build configuration files for all platforms+targets+arch combinations, users should call
```
scons vsproj=yes platform=XXX target=YYY [other build flags]
```
for each combination of platform+target[+arch]. This will generate the relevant vs project files but
skip the build process, so that project files can be quickly generated without waiting for a command line
build. This lets project files be quickly generated even if there are build errors.
All possible combinations of platform+target are created in the solution file by default, but they
won't do anything until each one is set up with a scons vsproj=yes command for the respective platform
in the appropriate command line. This lets users only generate the combinations they need, and VS
won't have to parse settings for other combos.
Only platforms that opt in to vs proj generation by having a msvs.py file in the platform folder are included.
Platforms with a msvs.py file will be added to the solution, but only the current active platform+target+arch
will have a build configuration generated, because we only know what the right defines/includes/flags/etc are
on the active build target currently being processed by scons.
Platforms that don't support an editor target will have a dummy editor target that won't do anything on build,
but will have the files and configuration for the windows editor target.
To generate AND build from the command line, run
```
scons vsproj=yes vsproj_gen_only=no
```
2023-11-14 13:39:44 +01:00
|
|
|
sources += common_win_wrap + res_wrap_obj
|
2022-10-14 12:18:25 +02:00
|
|
|
|
2015-11-08 23:53:58 +01:00
|
|
|
# Microsoft Visual Studio Project Generation
|
2020-03-30 08:28:32 +02:00
|
|
|
if env["vsproj"]:
|
2020-09-19 16:39:11 +02:00
|
|
|
env.vs_srcs += ["platform/windows/" + res_file]
|
|
|
|
env.vs_srcs += ["platform/windows/godot.natvis"]
|
2016-10-30 18:44:57 +01:00
|
|
|
for x in common_win:
|
2020-09-19 16:39:11 +02:00
|
|
|
env.vs_srcs += ["platform/windows/" + str(x)]
|
2022-10-14 12:18:25 +02:00
|
|
|
if env["windows_subsystem"] == "gui":
|
|
|
|
for x in common_win_wrap:
|
|
|
|
env.vs_srcs += ["platform/windows/" + str(x)]
|
2017-09-13 19:32:24 +02:00
|
|
|
|
2023-01-09 16:56:16 +01:00
|
|
|
if env["d3d12"]:
|
2023-12-13 08:57:51 +01:00
|
|
|
dxc_target_aliases = {
|
|
|
|
"x86_32": "x86",
|
|
|
|
"x86_64": "x64",
|
|
|
|
"arm32": "arm",
|
|
|
|
"arm64": "arm64",
|
|
|
|
}
|
|
|
|
dxc_arch_subdir = dxc_target_aliases[env["arch"]]
|
|
|
|
|
|
|
|
agility_target_aliases = {
|
|
|
|
"x86_32": "win32",
|
|
|
|
"x86_64": "x64",
|
|
|
|
"arm32": "arm",
|
|
|
|
"arm64": "arm64",
|
|
|
|
}
|
|
|
|
agility_arch_subdir = agility_target_aliases[env["arch"]]
|
|
|
|
|
2023-01-09 16:56:16 +01:00
|
|
|
# Used in cases where we can have multiple archs side-by-side.
|
2023-12-13 08:57:51 +01:00
|
|
|
arch_bin_dir = "#bin/" + env["arch"]
|
2023-01-09 16:56:16 +01:00
|
|
|
|
|
|
|
# DXC
|
2024-01-26 18:02:06 +01:00
|
|
|
if env["dxc_path"] != "" and os.path.exists(env["dxc_path"]):
|
2023-01-09 16:56:16 +01:00
|
|
|
dxc_dll = "dxil.dll"
|
|
|
|
# Whether this one is loaded from arch-specific directory or not can be determined at runtime.
|
|
|
|
# Let's copy to both and let the user decide the distribution model.
|
|
|
|
for v in ["#bin", arch_bin_dir]:
|
|
|
|
env.Command(
|
2023-12-13 08:57:51 +01:00
|
|
|
v + "/" + dxc_dll,
|
|
|
|
env["dxc_path"] + "/bin/" + dxc_arch_subdir + "/" + dxc_dll,
|
|
|
|
Copy("$TARGET", "$SOURCE"),
|
2023-01-09 16:56:16 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
# Agility SDK
|
2023-12-13 17:58:38 +01:00
|
|
|
if env["agility_sdk_path"] != "" and os.path.exists(env["agility_sdk_path"]):
|
2023-01-09 16:56:16 +01:00
|
|
|
agility_dlls = ["D3D12Core.dll", "d3d12SDKLayers.dll"]
|
|
|
|
# Whether these are loaded from arch-specific directory or not has to be known at build time.
|
|
|
|
target_dir = arch_bin_dir if env["agility_sdk_multiarch"] else "#bin"
|
|
|
|
for dll in agility_dlls:
|
|
|
|
env.Command(
|
|
|
|
target_dir + "/" + dll,
|
2023-12-13 08:57:51 +01:00
|
|
|
env["agility_sdk_path"] + "/build/native/bin/" + agility_arch_subdir + "/" + dll,
|
2023-01-09 16:56:16 +01:00
|
|
|
Copy("$TARGET", "$SOURCE"),
|
|
|
|
)
|
|
|
|
|
|
|
|
# PIX
|
2024-01-26 18:02:06 +01:00
|
|
|
if env["use_pix"]:
|
2023-01-09 16:56:16 +01:00
|
|
|
pix_dll = "WinPixEventRuntime.dll"
|
|
|
|
env.Command(
|
2023-12-13 08:57:51 +01:00
|
|
|
"#bin/" + pix_dll,
|
|
|
|
env["pix_path"] + "/bin/" + dxc_arch_subdir + "/" + pix_dll,
|
|
|
|
Copy("$TARGET", "$SOURCE"),
|
2023-01-09 16:56:16 +01:00
|
|
|
)
|
|
|
|
|
2017-09-13 19:32:24 +02:00
|
|
|
if not os.getenv("VCINSTALLDIR"):
|
2021-02-08 08:52:21 +01:00
|
|
|
if env["debug_symbols"] and env["separate_debug_symbols"]:
|
2018-03-17 23:23:55 +01:00
|
|
|
env.AddPostAction(prog, run_in_subprocess(platform_windows_builders.make_debug_mingw))
|
2022-10-14 12:18:25 +02:00
|
|
|
if env["windows_subsystem"] == "gui":
|
|
|
|
env.AddPostAction(prog_wrap, run_in_subprocess(platform_windows_builders.make_debug_mingw))
|
Add new VS proj generation logic that supports any platform that wants to opt in
Custom Visual Studio project generation logic that supports any platform that has a msvs.py
script, so Visual Studio can be used to run scons for any platform, with the right defines per target.
Invoked with `scons vsproj=yes`
To generate build configuration files for all platforms+targets+arch combinations, users should call
```
scons vsproj=yes platform=XXX target=YYY [other build flags]
```
for each combination of platform+target[+arch]. This will generate the relevant vs project files but
skip the build process, so that project files can be quickly generated without waiting for a command line
build. This lets project files be quickly generated even if there are build errors.
All possible combinations of platform+target are created in the solution file by default, but they
won't do anything until each one is set up with a scons vsproj=yes command for the respective platform
in the appropriate command line. This lets users only generate the combinations they need, and VS
won't have to parse settings for other combos.
Only platforms that opt in to vs proj generation by having a msvs.py file in the platform folder are included.
Platforms with a msvs.py file will be added to the solution, but only the current active platform+target+arch
will have a build configuration generated, because we only know what the right defines/includes/flags/etc are
on the active build target currently being processed by scons.
Platforms that don't support an editor target will have a dummy editor target that won't do anything on build,
but will have the files and configuration for the windows editor target.
To generate AND build from the command line, run
```
scons vsproj=yes vsproj_gen_only=no
```
2023-11-14 13:39:44 +01:00
|
|
|
|
|
|
|
env.platform_sources += sources
|