Skip to content

User/jvalesmena/old target builds#1396

Draft
5an7y-Microsoft wants to merge 6 commits into
mainfrom
user/jvalesmena/old-target-builds
Draft

User/jvalesmena/old target builds#1396
5an7y-Microsoft wants to merge 6 commits into
mainfrom
user/jvalesmena/old-target-builds

Conversation

@5an7y-Microsoft

Copy link
Copy Markdown
Contributor

No description provided.

5an7y and others added 6 commits June 22, 2026 12:38
Add a validated -TargetVersion parameter (also settable via the
WDS_TargetVersion environment variable) so samples can be built for older
target OS versions. Valid values come from the WDK DriverGeneral.xml rule
and default to the latest, Windows10:
  Windows10 (Windows 10 or higher), WindowsV6.3 (Windows 8.1),
  Windows8 (Windows 8), Windows7 (Windows 7).

The value is threaded through Build-SingleSample into the msbuild
invocation (replacing the hard-coded TargetVersion=Windows10) and across
the parallel runspace, and is surfaced in the build plan, final summary,
and HTML report title. Document the new parameter in the script help and
Building-Locally.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add an optional TargetVersions column to exclusions.csv so an exclusion can
be limited to specific target OS versions (e.g. exclude ARM only when
building Windows8). The column holds a ';'-separated list of -like patterns
matched against -TargetVersion; blank or '*' means all versions, so every
existing row stays applicable to all targets.

Import-SampleExclusions now takes -TargetVersion and filters rows by it at
load time (alongside the existing MinBuild/MaxBuild range); a missing column
is treated as '*' for backward compatibility. Document the new column and an
example in Building-Locally.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Expose the WDK '_NT_TARGET_VERSION' property (the OS version of the libraries
the driver links against) as -NtTargetVersion / WDS_NtTargetVersion. Unlike
-TargetVersion (Target OS Version), this does not change the platform model, so
Universal/Windows Driver samples keep building on Windows 10 while linking
against an older library set.

The parameter accepts the Windows build number (e.g. 10.0.22000), maps it to the
NTDDI code from the WDK DriverGeneral.xml rule, and passes -p:_NT_TARGET_VERSION
to msbuild (threaded through Build-SingleSample and the parallel runspace). It
defaults to the latest (10.0.28000) and is surfaced in the build plan, summary,
and HTML report title. Documented in Building-Locally.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Exclusions:
- Add MinNtTargetVersion/MaxNtTargetVersion columns to exclusions.csv so a row can apply
  only within an _NT_TARGET_VERSION build-number range (parsed from -NtTargetVersion, e.g.
  22000 from 10.0.22000). Import-SampleExclusions filters this range at load time alongside
  the existing build-number range; blank = unbounded.
- Exclude the samples that fail only when linking against older library sets, with the
  reason taken from the build logs: audio.sysvad (<=22000, KSJACK_DESCRIPTION3);
  network.netadaptercx.netvadapter and network.wlan.wificx (<=22621, NDIS/DDI version);
  powerlimit.plclient/plpolicy (<=22621, POWER_LIMIT_ATTRIBUTES); storage classpnp/storahci
  (<=22621, STOR_ADDRESS_TYPE_NVME, Debug-only) and storage.msdsm (Debug|x64). usb.usbview is
  intentionally NOT excluded: it fails on every version for a known host reason (missing
  .NET 4.7.2/4.8.1 targeting packs).

CI:
- ci.yml and ci-pr.yml: add _NT_TARGET_VERSION as a manual matrix axis (4 newest versions,
  latest-first) so each version x configuration x platform runs on its own parallel runner.
- Build-Samples.ps1 and Join-CsvReports.ps1 now write an easy-to-scan Markdown summary to
  GITHUB_STEP_SUMMARY: each build job shows counts and a failures table with the first error;
  the report job shows per-version totals and a consolidated failures list, plus the
  colour-coded sample x version HTML/CSV overview.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Remove the -TargetVersion parameter and all its plumbing from Build-Samples.ps1 (restoring
  the original hard-coded -p:TargetVersion=Windows10), and drop the TargetVersions column from
  exclusions.csv and Import-SampleExclusions. Only _NT_TARGET_VERSION remains exposed.
- Add Get-NtTargetVersions.ps1, which auto-discovers the valid _NT_TARGET_VERSION values (and
  their NTDDI codes) by parsing the active WDK's DriverGeneral.xml rule. Build-Samples.ps1 uses
  it to validate -NtTargetVersion, default to the latest, and map to the msbuild code, so a new
  WDK version needs no script change (accepts '10.0.<build>' or the short '<build>' tag).
- CI: ci.yml and ci-pr.yml gain a 'discover' job that emits the newest-N versions as JSON; the
  build matrix consumes it via fromJSON, so there is no hand-maintained version list anywhere.
  Build-ChangedSamples.ps1 treats Get-NtTargetVersions.ps1 as a full-build trigger.
- Docs updated accordingly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Remove the hand-maintained _NT_TARGET_VERSION -> friendly-name map (latest/24H2/...)
  from Join-CsvReports.ps1, along with its "Release" column in the HTML and step-summary
  tables; those labels cannot be auto-discovered.
- Stop hardcoding a version in the helper defaults: Import-SampleExclusions' -NtTargetVersion
  now defaults to empty (treated as the latest, so no NT-scoped row applies), and
  Build-SingleSample's -NtTargetVersionCode has no hardcoded code (the resolved value is
  always passed in). Blank MaxNtTargetVersion now uses [int]::MaxValue so 'latest'/empty
  matches the newest version's exclusion set.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

2 participants