diff options
author | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-03 10:29:03 +0100 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-03 10:29:03 +0100 |
commit | eb7535ee4459b4422105ef65abef5bde1c83e472 (patch) | |
tree | 209879518de2fa59b4c3e7be40b8c8bb4046275f /README | |
parent | d337d00183c27619f1eb4a84b06476658a4b7355 (diff) | |
download | libmnl-eb7535ee4459b4422105ef65abef5bde1c83e472.tar.gz libmnl-eb7535ee4459b4422105ef65abef5bde1c83e472.zip |
doc: don't show up EXPORT_SYMBOL in doxygen
Patrick reports that the doxygen output shows up EXPORT_SYMBOL
and tells how to fix this:
> I just noticed the EXPORT_SYMBOLs in libmnl showing up in
> the doxygen output. Just in case you want to avoid this,
> what I'm doing in libdect is (besides the appopriate linker
> flags):
>
> #define __visible __attribute__((visibility("default")))
>
> #define EXPORT_SYMBOL(x) typeof(x) (x) __visible
>
>
> This allows to use EXPORT_SYMBOL as in the kernel, IOW
> after the function definition.
This patch also removes -Wredundant-decls to avoid a warning in every
single use of this new approach.
Now, this looks more like the Linux kernel way of exporting symbols.
Reported-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions