Windows 7 build path: CEF/dullahan 109 + Win7 build target (separate build flavour) #800
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#800
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a separate Windows 7 build path: its own build flavour, installer and channel, next to the normal Windows build, for users who are still on Windows 7 SP1.
Accepted trade-off (owner decision): this build runs an old Chromium (CEF 109) that no longer gets security patches. Users who stay on Windows 7 are already running an unpatched OS knowingly, so this is acceptable. The installer, download page and release notes should say so plainly.
What's needed:
scripts/3p/manifest.py), selected only by the Win7 flavour.indra/CMakePresets.json) withWINVER=_WIN32_WINNT=0x0601instead of0x0A00(indra/cmake/LLBuildFlags.cmake:32).GetProcAddressfallbacks the wayllthread.cppandllwindebug.cppalready do forSetThreadDescription/GetThreadDescription..forgejo/workflows/release.yml(Windows cross build with the Win7 preset + CEF 109), its own release asset and update channel, so the auto-updater never moves a Win7 install onto the Windows 10 build.