On Sat, Sep 18, 2010 at 3:52 PM, Ozkan Sezer wrote:
> On Sat, Sep 18, 2010 at 7:17 PM, Wolfgang Glas wrote:
>> On 2010-09-18 18:03, NightStrike wrote:
>>> On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer wrote:
On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
>>
>> [snip]
>>
There is
On Sun, Sep 19, 2010 at 9:54 AM, JonY wrote:
> All the headers provided under our include directory are
> already part of sdk, therefore I don't know how a separation
> can be possible.
>
> Admins?
>
Personally, I think deviating from MS is a bad idea. If ms puts it in
On 9/19/2010 09:57, Xiaofan Chen wrote:
> On Sun, Sep 19, 2010 at 9:44 AM, Xiaofan Chen wrote:
>> On Sun, Sep 19, 2010 at 9:03 AM, JonY wrote:
All the headers provided under our include directory are
already part of sdk, therefore I don't know how a separation
can be possible.
On Sun, Sep 19, 2010 at 10:04 AM, Dongsheng Song
wrote:
> On Sun, Sep 19, 2010 at 07:50, Ozkan Sezer wrote:
>>
>> AFAIK, usb.h is out of ddk because it is part of ms platform sdk,
>> therefore, it _needs_ to be out of a ddk subdirectory for proper
>> compatibility.
>
> No, usb.h is in MS WDK 7.1
On Sun, Sep 19, 2010 at 07:50, Ozkan Sezer wrote:
>
> AFAIK, usb.h is out of ddk because it is part of ms platform sdk,
> therefore, it _needs_ to be out of a ddk subdirectory for proper
> compatibility.
>
No, usb.h is in MS WDK 7.1 now:
C:\opt\WinDDK\7.1\inc\api>dir *usb*
驱动器 C 中的卷没有标签。
卷的序列
On Sun, Sep 19, 2010 at 9:44 AM, Xiaofan Chen wrote:
> On Sun, Sep 19, 2010 at 9:03 AM, JonY wrote:
>>> All the headers provided under our include directory are
>>> already part of sdk, therefore I don't know how a separation
>>> can be possible.
>>>
>>> Admins?
>>>
>> Personally, I think deviati
On Sun, Sep 19, 2010 at 9:03 AM, JonY wrote:
>> All the headers provided under our include directory are
>> already part of sdk, therefore I don't know how a separation
>> can be possible.
>>
>> Admins?
>>
> Personally, I think deviating from MS is a bad idea. If ms puts it in the
> normal psdk, s
On 9/19/2010 08:00, Ozkan Sezer wrote:
> On Sun, Sep 19, 2010 at 2:56 AM, Xiaofan Chen wrote:
>> On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer wrote:
>>> On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen wrote:
I think the MinGW-w64 newly included usb.h will break
many existing software whi
On Sun, Sep 19, 2010 at 2:56 AM, Xiaofan Chen wrote:
> On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer wrote:
>> On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen wrote:
>>> I think the MinGW-w64 newly included usb.h will break
>>> many existing software which uses libusb-win32. For
>>> example, libftd
On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer wrote:
> On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen wrote:
>> I think the MinGW-w64 newly included usb.h will break
>> many existing software which uses libusb-win32. For
>> example, libftdi's header is called ftdi.h which includes .
>> libusb and l
On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen wrote:
> On Sun, Sep 12, 2010 at 5:34 PM, Xiaofan Chen wrote:
>> On Thu, Sep 9, 2010 at 3:53 AM, Ozkan Sezer wrote:
>>> 2. the name of your src/usb.h is, well, usb.h, and it conflicts, ie.
>>> searched before the system provided usb.h. Therefore, it
On Sun, Sep 12, 2010 at 5:34 PM, Xiaofan Chen wrote:
> On Thu, Sep 9, 2010 at 3:53 AM, Ozkan Sezer wrote:
>> 2. the name of your src/usb.h is, well, usb.h, and it conflicts, ie.
>> searched before the system provided usb.h. Therefore, it must be
>> renamed to something else. For my own tests, I
On 2010-09-18 21:52, Ozkan Sezer wrote:
> On Sat, Sep 18, 2010 at 7:17 PM, Wolfgang Glas wrote:
>> On 2010-09-18 18:03, NightStrike wrote:
>>> On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer wrote:
On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
>>
>> [snip]
>>
There is an optional s
On Sat, Sep 18, 2010 at 7:17 PM, Wolfgang Glas wrote:
> On 2010-09-18 18:03, NightStrike wrote:
>> On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer wrote:
>>> On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
>
> [snip]
>
>>> There is an optional small package in them, pr45300.zip,
>>> which is a
On 2010-09-18 18:03, NightStrike wrote:
> On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer wrote:
>> On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
[snip]
>> There is an optional small package in them, pr45300.zip,
>> which is an update for the C++ headers cstdio, cstdlib and
>> cwchar, fixin
On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer wrote:
> On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
>> I updated my custom w32/w64 native and cross-compiler build with gcc-4.4
>> with several backports and fixes from mainstream, and put them under the
>> mingw-w64 sf.net file release syste
On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer wrote:
> I updated my custom w32/w64 native and cross-compiler build with gcc-4.4
> with several backports and fixes from mainstream, and put them under the
> mingw-w64 sf.net file release system under the subdirectories:
> - Toolchain sources -> Perso
On 16/09/2010 12:23, Ozkan Sezer wrote:
> On Thu, Sep 16, 2010 at 1:02 PM, G E Naganna wrote:
>> Hi all,
>>
>>I am not able to generate GLEW libraries from MinGW-w64. I did
>> not find Makefile.mingw64 in config folder so I compiled by using Msys. I
>> am getting following error.
>>
> I have built a toolchain using attached "script", and while using my
> in-progress fancy build script, I noticed that while compiling ppl, the
> *.la files in lib64 contained the following:
>
> # Directory that this library needs to be installed in:
> libdir='/home/ruben/mingw64/build/mi
Hi,
I have built a toolchain using attached "script", and while using my
in-progress fancy build script, I noticed that while compiling ppl, the *.la
files in lib64 contained the following:
# Directory that this library needs to be installed in:
> libdir='/home/ruben/mingw64/build/mingw64/lib/../
20 matches
Mail list logo
