|author||Guy Harris <firstname.lastname@example.org>||2015-01-19 18:32:42 -0800|
|committer||Guy Harris <email@example.com>||2015-01-20 02:33:15 +0000|
Possibility -> certainty.
Change-Id: I03440a9b4ca13399aa14f3baaabd7aa40a843f28 Reviewed-on: https://code.wireshark.org/review/6678 Reviewed-by: Guy Harris <firstname.lastname@example.org>
Diffstat (limited to 'README.cmake')
1 files changed, 4 insertions, 3 deletions
diff --git a/README.cmake b/README.cmake
index 33481efcf8..038d9ee130 100644
@@ -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
- 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