[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] DirectShow Phonon Backend for Qt
From: |
Mark Brand |
Subject: |
Re: [Mingw-cross-env-list] DirectShow Phonon Backend for Qt |
Date: |
Sun, 28 Feb 2010 22:33:39 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100217 SUSE/3.0.2-6.1 Thunderbird/3.0.2 |
> As I already mentioned, it might be a good idea to:
>
> * manually download and unpack the latest official Microsoft
> DirectX stuff
>
> * correct the headers, and convert the libraries using the
> "reimp" tool (see the mailing list entry mentioned above)
>
> * repackage them, and ideally, include them directly into
> MinGW's official w32api package
>
> Of course, please correct me if I'm missing some important
> point here.
>
>
>> Would it be a good idea to put the "mingw-dshow" headers in a special
>> subdir of usr/i686-pc-mingw32/include so the names don't collide with
>> dx80_mgw headers? (Assuming the dx80_mgw headers stay where they are.)
>>
> I don't think it is a good idea to separate these DirectX headers.
> No build script expects multiple DirectX versions in separate
> directories. And I also don't think this is really necessary.
>
> What we need is _one_ coherent piece of DirectX headers and
> interface libs - either as part of the w32api package, or as
> a separate "directx" package.
>
This may be easier than we thought. The MinGW that comes with Nokia's Qt
SDK package already contains much more DirectX 9 support than the
"mingw-dshow" patch being considered by the MinGW project. Nokia's MinGW
is available as a separate file here:
ftp://ftp.qt.nokia.com/misc/MinGW-gcc440_1.zip
It would be easy to extract directx headers from this package. Does this
seem like a reasonable approach? I don't know yet if its possible to
completely replace dx80_mgw with this, but I have successfully built
mingw-cross-env after replacing just the headers needed to build the
Phonon backend.
-Mark