Building everything at once via the solution (tamic.slnx)

Besides the phased build (opening each project in turn — files win32/03…06 and win64/03…06), the package can be built as a whole from a single solution. In the source root (src\) there is a solution file in the new format, tamic.slnx, that includes all 12 projects (6 libraries + 6 programs) and knows the dependencies between them. Open it, pick a platform — build everything.

This is a second, optional method. The phased guides (01…08) remain valid: they are useful for understanding, debugging and building a single component. The combined solution is a convenient "build everything at once".

What .slnx is

.slnx is a Visual Studio solution in the new XML format (a successor to the textual .sln). It is more compact and readable. The format is supported by Visual Studio 2022 (17.10+) and Visual Studio 2026, which is used to build TMC Suite. Older Visual Studio versions cannot open .slnx.

Where the file is

<ROOT>\src\tamic.slnx

All paths inside the solution are relative to src\, so the file must reside exactly in src\. The property sheets (build\Common.props, LibOutput.props, ExeOutput.props) are attached in the projects themselves via relative paths and do not depend on the solution location — output still goes to dist\win32\… and dist\win64\….

What the solution contains and the build order

The solution contains all 12 projects and declared dependencies, so Visual Studio builds them in the correct order itself: first the required libraries, then the programs.

The order among the libraries does not matter (each .lib is independent), and the "program ← libraries" dependencies are enforced by the solution automatically. You do not need to track phases here as you do in the phased build.

Renaming the X-mode project

For the combined solution to work, the X-mode project file was renamed: kernels\PlanarRT_X\PlanRT_H.vcxproj → kernels\PlanarRT_X\PlanRT_X.vcxproj. The project name inside was already PlanRT_X, the build target is tmc_rtx.exe, so the rename merely brought the file name into agreement. The source files (PlanRT_H.cpp, PlanRT_H.h) were not renamed — the project references them. The local single-build solution for X was renamed to PlanRT_X.sln.

X-mode: the 6 macros are already set

The PlanRT_X.vcxproj project already contains the 6 X-mode preprocessor macros in all configurations (see win32/05-build-kernels.md, section 5.2). When building via the combined solution they are applied automatically — nothing extra needs to be set.

How to build everything (Visual Studio 2026)

1. Launch Visual Studio 2026.
2. File → Open → Project/Solution… and select src\tamic.slnx.
3. In the top toolbar set: - Configuration — Release; - Platform — Win32 (for the 32-bit build) or x64 (for the 64-bit build).
4. Build → Build Solution (F7). For a clean build — Build → Rebuild Solution.
5. Wait for the Output window: Build: 12 succeeded, 0 failed.

To get both bitnesses, repeat steps 3–5, switching the platform from Win32 to x64 (and vice versa).

_real precision: as in the phased build, src\Include\Typerth.h must have double precision active (#define _PREC_DOUBLE). This is a correctness condition for the X-mode (see win32/07-troubleshooting.md, § 7.8). The combined solution does not affect this — check the header before building.

Verifying the result

After building for both platforms, the output folders should contain:

dist\win32\lib\  and  dist\win64\lib\   → 6 .lib files each
dist\win32\bin\  and  dist\win64\bin\   → 6 .exe files each

The composition is the same as in the phased build (win32/06-build-fieldview.md, section 6.4; win64/06-build-fieldview.md, section 6.4).

Building from the command line (optional)

In Visual Studio 2026, building a .slnx via msbuild is available:

msbuild src\tamic.slnx /p:Configuration=Release /p:Platform=Win32
msbuild src\tamic.slnx /p:Configuration=Release /p:Platform=x64

Direct .slnx building from msbuild is supported only by sufficiently new tooling versions (VS 2022 17.13+/2026). If your command line does not understand .slnx, build from the Visual Studio IDE (the steps above) or use the phased .sln files of the individual projects.

Which method to choose when