[sane-devel] [RFC] On libsane symbols visibility

[Ilia Sotnikov]

On 5/8/07, Julien BLACHE <jb at jblache.org> wrote:
> SANE traditionally builds with non-gcc compilers too, so this is kind
> of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it,
> YMMV) :)
>

Then for such compilers we'll definitely need to use some #ifdef's.

> Backends that use multiple files usually #include them (see the
> snapscan backend, for instance) to workaround this limitation.
>

Yes, I saw and used that solution. What about marking symbols
explicitly when compiling under native Windows and use no attributes
under other platforms? Otherwise we'll need to leave with
not-intended-to-but-exported symbols at least under Windows having
'make libcheck' complain about them.

-- 
 Ilia Sotnikov