User: guy
Date: 2006/02/11 09:15 PM
Log:
Add a routine to attempt to get the absolute pathname of the executable
file, strip off the last component to get the pathname of the directory
containing the executable file, and save it for future use. On Windows,
you can get that from the OS, but, on UN*X, you have to look at argv[0]
and derive the absolute path from that (argv[0] is not guaranteed to be
an absolute path, or even a path at all). (In addition, if you're
running from the build directory, you might have to strip off a ".libs/"
added to argv[0] as an artifact of the libtoolizing script.)
Use that in the About dialog, and use it to construct the path of
dumpcap.
Don't put quotes into the path of dumpcap; you don't have to quote
strings with spaces in them when handing them to execvp and, in fact,
you *mustn't* quote them, as the quotes will be treated as part of the
pathname.
Directory: /trunk/epan/
Changes Path Action
+224 -58 filesystem.c Modified
+22 -11 filesystem.h Modified
Directory: /trunk/gtk/
Changes Path Action
+2 -4 about_dlg.c Modified
+5 -3 main.c Modified
Directory: /trunk/
Changes Path Action
+2 -4 capture_sync.c Modified
+0 -1 globals.h Modified
http://anonsvn.ethereal.com/viewcvs/viewcvs.py?rev=17267&view=rev