"compat.h" is for platform specific but module agnostic definitions... so if you don't like them all being stuffed in one file, then perhaps a win32_compat.h osx_compat.h linux_compat.h bsd_compat.h would be more to your liking? ... and for shared/related definitions ( as exist for win32/osx in many instances), then either duplicate it, or both of these could include there respective "requirements".... eg a compat_uint.h compat_sleep.h compat_xxx.h .... ?<br>
<br>How far do you want to take it?<br><br>Buzz.<br><br><br><div class="gmail_quote">On Wed, Jan 28, 2009 at 8:17 AM, Isaac Richards <span dir="ltr"><<a href="mailto:ijr@case.edu">ijr@case.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Tuesday 27 January 2009 4:57:16 pm Nigel Pearson wrote:<br>
> > libavcodec cannot depend on stuff in libmythdb.<br>
><br>
> It doesn't really create a circular dependency<br>
> (no API or library stuff), but yes, good point.<br>
><br>
> For now, OK to just create libavutil/compat.h<br>
> 'til I get to the bottom of FFmpeg MinGW build hacks?<br>
<br>
</div>Rather not, since it should already be supported..<br>
<br>
There's gotta be a better solution to porting issues than sticking a ton of<br>
unrelated stuff into one header and including that everywhere.<br>
<font color="#888888"><br>
Isaac<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
mythtv-dev mailing list<br>
<a href="mailto:mythtv-dev@mythtv.org">mythtv-dev@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br>
</div></div></blockquote></div><br>