Re: why do we install all system headers?

On Thu, Aug 17, 2006 at 01:32:36AM +0200, Thomas Anders wrote:
> is there a good reason why "make install" currently installs all of
> include/net-snmp/system/*.h and not just the one(s) for the system in question?
> Even cross-compiling only has a *single* target system, so why? Is it only to
> save us from having to figure out which one we need (since for some systems they
> are nested)?

I have less experience porting Net-SNMP than the rest of you, but it
strikes me as highly counterproductive to spend any time on this kind
of optimization.

Organizing the *system-provided* header files for a build is a hard
problem (FreeBSD has been awful), but one must put in the time anyway:
there is no magic shortcut that Just Makes It Work.

Organizing the *library-provided* header files does indeed have a
magic shortcut that Just Makes It Work: ship them all.

The upside:

- include/net-snmp/system/ has a few less files

The downside:

- no saving on the tarball size (need to ship them anyway)
- much more complicated ./configure configuration
- ongoing maintenance nightmare and source of bug reports

Steve

---
Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561
www.unixwiz.net | Tustin, Calif. USA | Microsoft MVP | steve@unixwiz.net

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders