[FFmpeg-devel] Fwd: [PATCH] Support alternative spellings of the inline keyword.
michaelni at gmx.at
Sun Jun 17 01:08:59 CEST 2012
On Sat, Jun 16, 2012 at 06:05:03PM -0400, Ronald S. Bultje wrote:
> same here, part of a MSVC port.
> ---------- Forwarded message ----------
> From: Ronald S. Bultje <rsbultje at gmail.com>
> Date: Fri, Jun 15, 2012 at 7:04 PM
> Subject: [PATCH] Support alternative spellings of the inline keyword.
> To: libav-devel at libav.org
> Cc: "Ronald S. Bultje" <rsbultje at gmail.com>
> From: "Ronald S. Bultje" <rsbultje at gmail.com>
> This is similar to how we support e.g. __restrict as an alternative for
> restrict, and allows us to support compilers that use __inline instead
> of inline. The define is placed in avconfig.h instead of config.h since
> we use inline in public header files.
> #ifndef AVUTIL_AVCONFIG_H
> #define AVUTIL_AVCONFIG_H
> +#define inline $_inline
Is this safe if ffmpeg is compiled and installed with one compiler
and an application with a different compiler ?
I mean configure is run with one compiler but a application that may
include the header and thus #define inline (__)inline could use a
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the ffmpeg-devel