On 2/9/2012 1:58 AM, Ozkan Sezer wrote:
> It is already among the headers, but not under a "ddk" subdirectory.
> Just include it like
Thank you, I realized this for myself just before you replied.
Apologies for not digging deeper first.
Best regards,
Kyle Schwarz
On Thu, Feb 9, 2012 at 8:42 AM, Kyle wrote:
> Hello,
>
> I'm trying to compile libcdio with the latest MinGW-w64.
>
> I get:
> fatal error: ddk/ntddcdrm.h: No such file or directory
>
> I see that ntddcdrm.h is part of MinGW, but not MinGW-w64.
>
> Is there any plans to implement it, or am I out o
Hello,
I'm trying to compile libcdio with the latest MinGW-w64.
I get:
fatal error: ddk/ntddcdrm.h: No such file or directory
I see that ntddcdrm.h is part of MinGW, but not MinGW-w64.
Is there any plans to implement it, or am I out of luck for libcdio?
Best regards,
Kyle Schwarz
-
On Wed, Feb 8, 2012 at 4:27 AM, Davidson, Josh wrote:
>
>
> “The procedure entry point vsnprintf could not be located in the dynamic
> link library msvcrt.dll”
>
>
>
> I know this error has been posted to the mailing list before, but I’m
> wondering if there is any way of working around it in bina
2012/2/8 Davidson, Josh :
>
>
> “The procedure entry point vsnprintf could not be located in the dynamic
> link library msvcrt.dll”
>
>
>
> I know this error has been posted to the mailing list before, but I’m
> wondering if there is any way of working around it in binary distributions.
> I’m using
"The procedure entry point vsnprintf could not be located in the dynamic link
library msvcrt.dll"
I know this error has been posted to the mailing list before, but I'm wondering
if there is any way of working around it in binary distributions. I'm using
the latest automated build (mingw-w32-b
