"Ilia Sotnikov" <[email protected]> wrote: > 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.
I don't know if a clean libcheck is mandatory/enforced as far as native win32 is concerned; I think it can't be avoided if part of the portable function library is used. JB. -- Julien BLACHE <http://www.jblache.org> <[email protected]> GPG KeyID 0xF5D65169
