Mach does not detect usable Windows SDK directory behind unusable Windows SDK directory
Categories
(Firefox Build System :: General, task)
Tracking
(firefox101 fixed)
| Tracking | Status | |
|---|---|---|
| firefox101 | --- | fixed |
People
(Reporter: rkraesig, Assigned: rkraesig)
Details
Attachments
(1 file)
Installing the WDK without its associated SDK [0] results in a partial installation of that SDK (10.0.22000.0) not usable for actually compiling code.
If such a partial installation is present, Mach will error out, ignoring the usable fully-installed SDK (10.0.19041.0) which is present "behind" it.
[0] Which may sound like a bizarre thing to do; but I did it specifically to get access to one of the tools bundled with it (which works just fine without the associated SDK).
|
Assignee | |
Comment 1•2 years ago
|
||
get_sdk_dirs does not actually return multiple candidate SDK
directories. This can lead to mach not finding a usable SDK dir if an
unusable one conceals it.
(This state of affairs was observed after installing the latest WDK
without its matching SDK -- which is something one might do just to get
WDK-associated tools like TraceView.)
|
||
Updated•2 years ago
|
|
|
||
Updated•2 years ago
|
|
|
||
Updated•2 years ago
|
Pushed by rkraesig@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a8788f15fc9a mach configure: check all candidate SDK directories r=mhentges
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
|
||
Updated•2 years ago
|
Description
•