diff options
author | Guy Harris <guy@alum.mit.edu> | 2014-07-31 13:55:56 -0700 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2014-07-31 20:56:29 +0000 |
commit | 43a81b61395358d93a3f859e9058dfd7ecc39a7e (patch) | |
tree | b747da0b3d6f84eb54e097b1338db0ed54ee7185 | |
parent | 9505d3a7bcff2e884e9c1d4a004997def81fddff (diff) | |
download | wireshark-43a81b61395358d93a3f859e9058dfd7ecc39a7e.tar.gz |
Add some information on running from the build directory.
Change-Id: I6c01141cd02af358152d007175ec0b51357e42b3
Reviewed-on: https://code.wireshark.org/review/3298
Reviewed-by: Guy Harris <guy@alum.mit.edu>
-rw-r--r-- | README.cmake | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/README.cmake b/README.cmake index 2b6fdea3b7..94b06a723f 100644 --- a/README.cmake +++ b/README.cmake @@ -127,10 +127,26 @@ What needs to be done? Solaris, Win32, Win64, ...) - Support building against an SDK for OS X. - Add support for cmake configurations. -- Get plugins loading when running *shark from the build directory. - Automatically figure out if *shark is running from the build directory (making WIRESHARK_RUN_FROM_BUILD_DIRECTORY unnecessary like it is with autofoo). + Sadly: + + $ file run/qtshark + run/qtshark: Mach-O 64-bit x86_64 executable + + so what you're running from the build directory is the executable + itself. autofoo includes libtool in our case, so what you're running + from the build directory is a script that then runs the executable, + and the executable is in a .libs directory; the code that checks for + "running from the build directory?" checks for that. + + We could perhaps check for the pathname containing "run/", although + that wouldn't help if we ran it while *in* the "run" directory; + getting an absolute path for the executable would be necessary for + that. +- Get plugins loading when running *shark from the build directory. + That might involve handling ".libs" and "run" differently. - Get cross-compilation working (or ensure it does). It works with autofoo. ... |