Open Bug 1256997 Opened 8 years ago Updated 2 years ago

Don't search registry for DirectX SDK

Categories

(Firefox Build System :: General, defect)

defect

Tracking

(Not tracked)

People

(Reporter: gps, Unassigned)

References

Details

The DirectX SDK used to be a standalone thing. In the version of the Windows SDK that we currently use to build Firefox, the DirectX SDK is included as part of the Windows SDK.

old-configure.in currently has code for finding the DirectX SDK by searching the Windows registry. This should no longer be necessary now that the DirectX SDK is part of the Windows SDK.

I'm blocking this on bug 1186060 because if we have to include an old version of the DirectX files to appease Windows XP support, that will be much easier once the toolchain is managed via tooltool (we can just add those old files to the archive and update the mozconfigs/configure to look in the appropriate location).
How to create a local build with XP support, then?
(In reply to Masatoshi Kimura [:emk] from comment #1)
> How to create a local build with XP support, then?

Good question. Do people still do that? Perhaps we could hard code the path to the DirectX SDK. To be honest, it still isn't entirely clear to me how certain DirectX/Angle files from the builders are leaking into our VS2015 build. That is something we'll need to figure out in time, as I would like no toolchain files installed on the Windows builders eventually. (Everything should come from tooltool.)
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.