Hi all-
I'm running into link problems because my project contains an application that
needs AgentX protocol support, but cannot link to the -lnetsnmpmibs library.
So, I'm volunteering to move that code from agent/mibgroup/agentx into the
agent directory. Here's what I'm thinking:
1. agent/mibgroup/agentx/*.c will be moved to agent/agentx_*.c as appropriate.
They will be compiled into -lnetsnmpagent.
2. agent/mibgroup/agentx/*.h will be refactored into new header files. Hopefully,
I will be able to split them between protocol, master, subagent and 'internal'.
The 'internal' header will live in agent/agentx.h and will not be installed.
3. --disable-agentx will be added to configure. (So will --enable-agentx, but it will
be enabled by default.) I'll find some way for the current --with-mib-modules
to be supported for backwards compatibility.
And here's what I don't know what to think (questions):
Q1. What are the 'external' interfaces to the master and subagent code? Does
this change dramatically when someone decides to implement the AgentX
mib (RFC2742)?
Q2. (How) should this be done for SMUX? (I'm not real clear on the purpose
of agent/mibgroup/smux/snmp_*.c)
Q3. Is there a best current practice for implementing backwards-compatibility
with the --with(-out)-mib-modules options to configure?
Q4. Am I a fool for trying to do this? (Someone else is doing it, I'm going to run
into horrible linking problems, ...)
ben
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
