Wireshark mailing list archives
Re: Keeping dumpcap lean and clean
From: Guy Harris <guy () alum mit edu>
Date: Mon, 3 Jan 2011 22:49:38 -0800
On Jan 3, 2011, at 10:14 PM, Jaap Keuter wrote:
... same question stands for Makefile.nmake, why is $(PYTHON_LIBS) included in the production rules for dumpcap?
Somebody copied-and-pasted {xxx}_CFLAGS = $(AM_CLEAN_CFLAGS) $(py_dissectors_dir) and the same stuff in Makefile.am, for some value of {xxx}? I'd say get rid of them, and wait for somebody to report a problem. No problem -> either there's no problem with removing them, or there's a problem but nobody cares enough for *us* to care. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Keeping dumpcap lean and clean Jaap Keuter (Jan 03)
- Re: Keeping dumpcap lean and clean Jaap Keuter (Jan 03)
- Re: Keeping dumpcap lean and clean Guy Harris (Jan 03)
- Re: Keeping dumpcap lean and clean Jaap Keuter (Jan 03)