> I'm running into link problems because my project contains an
> application that needs AgentX protocol support, but cannot link
> to the -lnetsnmpmibs library.
<Nods>
Not too unexpected.
This is one of a number of blocks of functionality that doesn't
really belong in the 'mibs' library.
> So, I'm volunteering to move that code from agent/mibgroup/agentx into
> the agent directory.
Actually, you probably don't need to move the files at all.
It should be sufficient to tweak the Makefiles so that the
mibgroup/agentx files are compiled and linked into the
main agent library instead.
Try the following:
- edit agent/Makefile.in and add the agentx-related objects
to the LIBAGENTOBJS and LLIBAGENTOBJS definitions
- run "configure --with-out-mib-modules=agentx"
- compile
That ought to move the AgentX support to the agent library
without needing to touch the code at all. You might need to
tweak things somewhere to invoke the 'init_agentx_config'
and 'init_subagent' routines, but that's all I can think of.
> Here's what I'm thinking:
[snip]
> 3. --disable-agentx will be added to configure.
That's the one bit that I've got reservations about.
Yes, it'll work fine.
But there are a handful of similar "pseudo-mib" modules
that are currently handled under mibgroup (so that they
can be included/excluded), but ideally belong in the main
agent library instead. But still with some way to
include or exclude them.
Things like the VACM and USM support, the handling of
trap destinations, etc. Most of these have a MIB interface
(which probably does belong in the mib library), but can
be used independently of this (e.g. via config directives
or hardcoded settings).
We've recently started to slowly disentangle them a bit,
but we don't really have a clean mechanism for deciding
what should and shouldn't be included within the agent-related
libraries. Ideally, I'd like to see a more flexible arrangement
than hard-wiring specific options into the configure script.
(It's enough of a mess as it is!)
Dave
-------------------------------------------------------
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
