Guenter wrote:
> so where end we then? With an ugly list of platform-specific ifdefs
Would it be better to create a new file, such as example.h, in order to keep
the example code clean and hide the actual build requirements in a header
that's common to all the examples and can contain whatever #ifdefs are
needed, be they application-like or library-like?
Also, to cope with unmet requirements, isn't #error designed for that?
Regards,
-- Mark Smith _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-develReceived on 2010-06-02