Michael Riepe wrote:
> Hi 'cutters,
> 
> David Coe wrote:
>> Hi list!
>>
>> Every so often I compile up dvbcut under Windows MinGW rather than rely 
>> on Ralph Glastetter's builds. Recently (somewhere after r154 I think) my 
>> compilation has failed with a missing "C:/MingW/include/stdlib.h".
>>
>> This has been hard-wired into dvbcut's version in /import/stdlib.h and 
>> will only suit the writer's own MinGW installation. Might it be better 
>> to have this as "/mingw/include/stdlib.h"? This is, at least, is the 
>> canonical location for the mingw compiler suite.
> 
> actually, there's a better fix: use gcc's #include_next feature. That
> will load MinGW's version of the file no matter where it is installed.
> The gcc dependency shouldn't be a problem because we're not using any
> other compiler on Windows anyway.
> 
> Welcome to r162,

Nope .. that doesn't work :-(. I'm getting bombs on undeclared 'malloc' 
and 'free', which means the system stdlib.h isn't being picked up.

As I understand it, #include_next traverses down the include directory 
list looking for the named file. For dvbcut this is:

-I../import  -I/usr/local/include -I/home/david/dvbcut/ffmpeg/include
  -I/home/david/dvbcut/ffmpeg/include/ffmpeg -I/usr/local/qt3/include -I.

so it would only work if the (idiosyncratic) /mingw/include were added 
to make's include list.

Regards

-- 
David


------------------------------------------------------------------------------
_______________________________________________
DVBCUT-user mailing list
DVBCUT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dvbcut-user

Reply via email to