[Libreoffice] using ATL with MSVC 2008 Express

[Regina Henschel]

Hi Thorsten,

Thorsten Behrens schrieb:
> Regina Henschel wrote:
>> It is not, that I would not be able to learn it, but I like to stay
>> in Calc or Draw. And there is already more stuff to learn and to do
>> than my time permits.
>>
> Hi Regina,
>
> sure, no prob - but maybe you could help extracting the information
> where the DDK installer stores its paths, so others can hack up the
> magic:

Yes. I have started that already yesterday evening. So here my results, 
for my WinXP-System. I haven't got a Window7, so cannot examine there.

>
> I suspect somewhere below these registry keys:
>   - HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft SDKs

No, that contains only
.NETFramework\v2.0 with REG_SZ with value C:\Programme\Microsoft Visual 
Studio 8\SDK\2.0\
and
Windows\v6.0A and Windows\v6.1 with path to C:\Programme\Microsoft 
SDKs\Windows\v6.0 and \v6.1 respectively.

>   - HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MicrosoftSDK/Directories
>   - HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MicrosoftSDK/InstalledSDKs

Those contain only information
C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2

I had tried that too. The "Microsoft Platform SDK for Windows Server 
2003 R2" contains a lot of the "atl"-things but at least one file is 
missing; I don't remember which one.

>
> could you hunt that down?

A search with WinDDK in the registry gives some results.

It seems that the driver kit is identified by a pair of IDs
 
{B4285279-1846-49B4-B8FD-B9EAF0FF17DA}:{68656B6B-555E-5459-5E5D-6363635E5F61}

1.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\KitSetup\configured-kits\{B4285279-1846-49B4-B8FD-B9EAF0FF17DA}\{68656B6B-555E-5459-5E5D-6363635E5F61}

key
     setup-install-location
value
     C:\WinDDK\7600.16385.1\

2.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WDKDocumentation\7600.091201\Setup
key
     BUILD
value
     C:\WinDDK\7600.16385.1\

But it might be, that the documentation is not installed.

3.
For nearly each file of the kit (>500!) an entry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\<a 
magic number>\ with
key
	B4285279-1846-49B4-B8FD-B9EAF0FF17DA
value
	<path to the file>

I think, that only the first is a usable registry item.


Another approach to find the kit might be to use the entry in (German WinXP)
C:\Programme\Gemeinsame Dateien\Microsoft KitSetup\Kit 
Definitions\{B4285279-1846-49B4-B8FD-B9EAF0FF17DA}\{68656B6B-555E-5459-5E5D-6363635E5F61}
and therein the file
SKOM_1-kit-identification.xml
which has the nodes
<KitInstallBasePath>%SYSTEMDRIVE%\WinDDK\</KitInstallBasePath>
and
<KitInstallSubdirectory>7600.16385.1</KitInstallSubdirectory>


But all will not help, if the files are copied to another place and the 
kit is uninstalled, as Mathias suggested on other place. I have not 
tested, whether that would work.

Auto-detecting is fine, but a parameter --with-winddk-home with user set 
value, for me "C:\WinDDK\7600.16385.1", from which the other four paths 
are generated, would already help.

Kind regards
Regina









>
> Thanks,
>
> -- Thorsten