osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Possibility -> certainty. 

Change-Id: I03440a9b4ca13399aa14f3baaabd7aa40a843f28
Reviewed-on: https://code.wireshark.org/review/6678
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2015-01-19 18:32:42 -08:00
parent f16e8fbebf
commit 8c15ac4636
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.cmake
View File

@ -176,9 +176,10 @@ What needs to be done?
won't find the relevant shared libraries.
We could perhaps check for the executable being in a "run" directory
instead, if the build drops it there. However, it might be possible
to copy the executable to another directory and have it run, so the
guarantee that it's in a "run" directory might not be as strong.
instead, if the build drops it there. However, it's possible, at
least on OS X, to copy the executable to another directory and have
it run, so the guarantee that it's in a "run" directory is not as
strong.
- Get plugins loading when running *shark from the build directory.
That might involve handling ".libs" and "run" differently. The chance
that a random directory the executable was ultimately placed in would