---- On Mon, 23 Jul 2018 21:33:00 +0100 Dagobert Michelsen <d...@opencsw.org> 
wrote ---- 
 > Hi Jan,
 > 
 > Am 23.07.2018 um 22:04 schrieb Jan Stary <h...@stare.cz>:
 > > 
 > > From both a sysadmin and user perspective, I find the GNU autotools
 > > amd CMake a major annoyance. Would you please consider doing what e.g.
 > > http://mandoc.bsd.lv/cgi-bin/cvsweb/configure does?
 > > 
 > > A simple, hand written shell script, with a set of obvious
 > > {test,compat}-*.c helpers. No dependency on anything, orders
 > > of multitude smaller and faster then a auto*-generated configure.
 > 
 > No - please! Handwritten configure scripts are the worst nightmare for
 > downstream packages as each package uses its own way to configure flags
 > for compilation, linkage, install relocation etc. This makes
 > packaging stuff hard as it requires specific adjustments of build
 > procedures. I maintain roughly 1600 packages and this would not be
 > possible when there were no standards. Autotools is far from perfect,
 > but it is a standard and after you figured something out it works for
 > hundreds of builds in the same way.

You had this exact discussion 2 weeks ago, didn't you? For the avoidance of 
doubt, this thread isn't about voting.

Autotools has historically been the build solution because tcpdump originates 
from the UNIX world, and used to compile and work on much more flavors than a 
typical modern software. AIX, HP-UX and Solaris are still around and configure 
works there.

Guy has [relatively] recently added cmake as an alternative build solution 
because, as far as I understand, it also supports Windows in a way that is 
simpler to maintain than autotools. I do not build any software on Windows and 
I do not use cmake to build any software, so this is my interpretation, feel 
free to correct.

Perhaps if someone had written down, in plain English, which specific steps it 
takes to compile tcpdump/libpcap, it would be easier to see if it can be done 
with a simple shell script.

-- 
    Denis Ovsienko


_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Reply via email to