>>>>> On Wed, 01 Feb 2006 16:20:40 +0100, Thomas Anders <[EMAIL PROTECTED]> >>>>> said:
Thomas> a) introduce some config_XXX in the mib module header files for the Thomas> *supported* platforms Thomas> b) introduce some config_XXX in the mib module header files for the Thomas> *unsupported* paltforms We have mechanisms for doing these. config_error and config_warning both allow you to mention problems. However, I think: 1) ifdefs is the right way to go; it's much more flexible than anything we could dream up and isn't prone to new parsing errors. 2) As to whether to do a) or b), I'd tend to think it's likely a case-by-case basis. Much of the time, for example, it might depend on the existence of a test/header/something and should be treated that way rather than using #if[n]def ARCH. If I was going to pick one to lean toward, it would probably be ifdeffing out unsupported platforms unless it's only known to work on 1-2. Thomas> c) do platform handling directly in configure[.in] Object strongly. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
