Visual Studio: C++ project and generator limits
Workspace, generation options and observed SCons diagnostics.
Visual Studio for C++ sources
Building requires a C++ toolchain rather than only a code editor. Install the required components through Desktop development with C++ and check supported tools against the build guide. This configures engine sources; game C# development uses the game project.
What SCons generates
In Source, vsproj=yes invokes the Visual Studio generator. vsproj_name selects the name, defaulting to reckfell. The generator uses misc/msvs/ templates to produce a solution, C++ project and configuration props.
| File or option | Purpose |
|---|---|
reckfell.sln | Solution containing project configurations. |
reckfell.vcxproj | Source project and configuration imports. |
reckfell.*.generated.props | Settings for a specific platform/target/arch combination. |
reckfell.vs.user.props | Local additions imported when the file exists. |
vsproj_gen_only | Defaults to true: generation exits before compilation. |
vsproj_props_only | Updates props without rewriting the solution and vcxproj. |
A generated solution does not mean the engine has been built. Current templates delegate build commands back to SCons. Specifying an output EXE name in the IDE does not change the filename produced by the build system. See Microsoft documentation for the external-build model.
Current source limitation
In isolation, generator helper glob_recursive_2 raised ImportError because it imports SCons.Entity, which SCons 4.11.1 does not provide. Shared helper glob_recursive has the same defect. The complete solution generator was not executed in this run. Do not treat the presence of a vsproj option as proof of successful generation.
Until the build helpers are repaired, sources can be opened as a folder for reading and editing. This does not promise configured builds or complete IntelliSense. If a solution already exists, check its origin and props freshness; an old file does not establish that the current generator works. See the IDE setup overview.
After generation is restored
- Choose the same platform/target/arch used for SCons configuration. The editor needs target editor; export templates use separate targets.
- Open the generated solution and confirm it imports props for that configuration. Combinations visible in a list do not mean settings for every platform have been generated.
- Inspect the actual build command and its environment. Successful indexing does not establish that the compiler, SDK and dependencies are available.
- Regenerate settings after configuration changes. Keep local additions separate from generated files that can be overwritten.
Debug symbols have a separate debug_symbols option; dev_build also enables DEV_ENABLED and affects other parameters. Do not treat them as interchangeable without understanding the build configuration.
Current templates, option values and helper failures were checked. Running all of SConstruct to generate a solution, building in Visual Studio and native debugger operation were not verified. The engine was unchanged.