Wireshark mailing list archives
WIRESHARK_RUN_FROM_BUILD_DIRECTORY for in-source CMake build
From: Tony Trinh <tony19 () gmail com>
Date: Wed, 20 Jun 2012 23:10:32 -0400
When I query the list of RADIUS fields from tshark, I see a different number of results as shown below. *in-source CMake build (tshark run from top-level source directory):* $ ./tshark -G fields | grep 'radius\.' | wc -l 89 $ WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 ./tshark -G fields | grep 'radius\.' | wc -l 8613 *out-of-source CMake build (tshark run from build directory):* $ ./tshark -G fields | grep 'radius\.' | wc -l 8613 *autotools build (tshark run from top-level source directory):* $ ./tshark -G fields | grep 'radius\.' | wc -l 8613 Why is the environment variable WIRESHARK_RUN_FROM_BUILD_DIRECTORYnecessary for the in-source CMake build but not in any other case?
___________________________________________________________________________ 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:
- WIRESHARK_RUN_FROM_BUILD_DIRECTORY for in-source CMake build Tony Trinh (Jun 20)
- Re: WIRESHARK_RUN_FROM_BUILD_DIRECTORY for in-source CMake build Jeff Morriss (Jun 21)
- Re: WIRESHARK_RUN_FROM_BUILD_DIRECTORY for in-source CMake build Guy Harris (Jun 21)
- Re: WIRESHARK_RUN_FROM_BUILD_DIRECTORY for in-source CMake build Jeff Morriss (Jun 21)