On tor, 2007-06-07 at 12:48 -0700, Need Help wrote:
> Are you recommending we hire a "NetSNMP consultant" to come in and
> explain what can be done to integrate NetSNMP into our environment?
> If so, I can mention it to my management, but I would assume they
> would first like to know what each command does internally to the
> files and NetSNMP environment to see if they can simply mirror what
> these commands do.
>
> Anyway, the "build" people here are experienced with integrating other
> applications into the build environment. They typically figure out
> what all the "setup" commands do internally and then add this
> "underlying" functionality into the build process.
>
> I would assume it might be hard to determine what each individual
> option does internally or how each option affects the system
> configuration for use by NetSNMP, but this is what I have been asked
> to try and figure out. Actually, to start, I am only interested in
> figuring out how hard it would be to mirror what "Configure", "make"
> and "make install" do ......
>
> Also, it would be nice to know whether it is a common practice to
> integrate NetSNMP into a build environment without using the
> "configure", "make", "make install", etc, etc.. commands which are
> normally used to get NetSNMP functioning properly.
What I would do if I were to incorporate netsnmp in my build environment
would be to:
* Treat Net-SNMP as a third party component
This means that I do not build it as part of regular builds,
instead it is built once in a blue moon when there are upgrades
from the provider that are of interest to me.
* Integrate it in my build system based on net-snmp-config
The flags that have to be added are provided by net-snmp-config,
especially the --cflags and --libs options are of interest but
please do run it and read the output of the --help option.
* Only use configure, make, make install when I had a new target
platform or a new net-snmp version
I do not want to build net-snmp just because I wish to build my
product.
I suppose your build people could live with this and go on from there.
> Steve Friedl <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 07, 2007 at 12:32:00PM -0700, Need Help wrote:
> > Ok, my company would like me to start discussing how to
> incorporate NetSNMP into the company's build environment. I
> explained the following stuff:
>
> Your company should probably retain a consultant experienced
> in these
> matters, because it's likely to rapidly wander outside the
> bounds of
> of the library itself, and what help you're likely to get
> here.
>
> Steve
>
>
> > - Indicated "./configure", "make" and "make install" were
> required for NetSNMP
> > - Indicated "snmp.conf" and "snmpd.conf" files exist to
> define stuff
> > - Indicated certain environment variables could be used if
> desired
> > - Indicated other stuff as well.... as much as I came across
> so far.... :>P
> >
> > During this discussion, the "build-production" people at my
> company informed me we can not perform the "configure" command
> as part of our "build process". Instead it would be necessary
> to understand exactly what the "configure" command (and I
> guess the "make" and "make install" commands as well) do
> "behind the scenes" so our build process and perform these
> exact steps ourselves. I was told we do not want to execute a
> script file with all of the required commands and options in
> it as well.
Somewhat extreme, but I can accept their position.
* configure checks various aspects of how your environment works
and adapts the net-snmp package to that.
* make compiles all source files based on the configure result.
* make install installs the finished result.
> > Anyway, is this a common approach to integrating NetSNMP
> into a business application (ie: not using the standard setup
> commands/options as part of the command line or in a script
> file)? It scares me not to use the standard steps to get
> NetSNMP configured/running. Perhaps someone can explain to me
> whether this is weird or not. If so, then perhaps you can give
> me a quick overview as to how NetSNMP should "normally" be
> integrated in a build system.
The important part is to differ between building net-snmp and building a
net-snmp client.
> > I understand no one knows how our build system works
> (neither do I), but any input into this topic would be greatly
> appreciated.
It is a pretty standard configure-based setup.
To build net-snmp you run configure; make; make install
To use net-snmp you just add the right include paths and libraries.
> > Is it crazy to think we can perform everything that
> "./configure", "make" and "make install" does oursleves
> without using those commands? Perhaps we do not need many of
> the things these commands do to set up NetSNMP?
Yes, it is crazy. There is no buisness value for you company in
reinventing that wheel.
> > I obviously had no answers for my company on this issue, so
> I am asking for help from people who have gone through this
> before.
/MF
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
