Closed Bug 718031 Opened 8 years ago Closed 8 years ago

Need to update Windows build slave image to include DirectShow SDK examples

Categories

(Release Engineering :: General, defect, P3)

x86
Windows 7
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jesup, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [opsi][buildslaves])

(copy from another bug on checking the licensing - we expect that not to be a problem; Legal is checking).  Note that this blocks progress on landing this to enable the "taking-a-picture" feature.

We're using the WebRTC libraries (http://www.webrtc.org/), which are primarily written by Google for multimedia work. On Windows, these libraries build some source files that ship with the Microsoft Windows SDK, the "DirectShow Base Classes":
http://msdn.microsoft.com/en-us/library/windows/desktop/dd375456%28v=VS.85%29.aspx

These samples ship as part of the Windows SDK:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8279
The Windows SDK that's currently installed on our build slaves did not have the samples installed. We'll probably need to re-run the installer to install the samples.
We actually never ran the installer, we extracted the required files/dirs manually.

Shouldn't be too hard to add this in, if its legally ok.
Ah, thanks for the info. If the installer wasn't run, does that mean the registry entries it creates aren't present? That's going to cause additional problems.
Looks like we did do at least some of the registry entries: http://hg.mozilla.org/build/opsi-package-sources/file/0c54e225977c/dx10sdk/CLIENT_DATA/dx10sdk.ins

I'll try to find an owner for this bug.
Priority: -- → P3
Whiteboard: [opsi][buildslaves]
from mtg w/randell, maire;

1) ted: are all the registry entries in comment#4 enough, or do we need additional registry entries?

2) RelEng will pull a machine from production, and lend it to Randell. He'll manually copy on the example code needed (not using the installer!), and verify that webRTC code builds as hoped. 

Assuming all that works ok, and bug#717008 is fixed, then we can schedule deployment onto production systems.
It doesn't look like the script in comment 4 covers the registry entry we need. The key we need is the one this Python script reads:
http://hg.mozilla.org/projects/alder/file/3a981cf610f7/media/webrtc/trunk/src/build/getsdksamplesdir.py#l7
HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0\WinSDKSamples
InstallationFolder
bug 717008 has been WONTFIXed in favor of an alternate implementation (bug 731407), so this has become WONTFIX as well.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.