Dave> It should be sufficient to tweak the Makefiles so that the
Dave> mibgroup/agentx files are compiled and linked into the
Dave> main agent library instead.
Wes> You know... that's actually a good idea as a more permanent
Wes> solution. We could just mark (somehow) certain files within the
Wes> mibgroup directory as stuff that should get compiled into the core
Wes> agent, and mark other files as true mib code.
You mean something like:
config_belongs_in( MIBLIB )
vs
config_belongs_in( AGENTLIB )
?vs
config_belongs_in( AGENT )
and then use that to build the lists of object files in the various
Makefiles?
(Probably with a 'configure' mechanism to override these assignments)
The main thing that springs to mind is a need to check that dependencies
only run one way. If a given code file "A" is marked as belonging in the
agent library (whether via "config_belongs_in" or dynamic configure flags,
or at the whim of some divine being), and this relies on routines in
another code file "B", which is marked as belonging in the MIB library,
then I suspect that B should probably be upgraded to be in the agent
library instead.
(But not vice versa)
> it has
> its other advantages which you just put in my head
Such as?
C'mon Wes, you know that your head isn't a safe repository for anything
important. At the very least share it with someone reliable like Katie.
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
