Hi,
This sounds all overly complicated. You could deduce which
executable/DLL is affected by you changes by unraveling the build
process, but it's much easier to build you own full installer.
Thanx,
Jaap
Greg Bell wrote:
Hello,
I'd like to make some modifications to Wireshark and package only the
modified/new DLL's (or other modified files) in my own installer. This
installer would then simply overwrite the original files from a stock
install.
My question is, how do I know which DLL's I must use based on the source
files I modified? I could make the source changes and see which files
have different time stamps, but is there a cleaner, more precise way? As
well, it seems wireshark.exe is always created with a new build - when
does a source change affect the exe?
For example, if I modify the following files:
C:\wireshark\file.c
C:\wireshark\print.c
C:\wireshark\print.h
C:\wireshark\gtk\menu.c
Which DLL's (or other install files) will I need to copy for my custom
install (on the target host)? Or am I just going about this the wrong way?
Thank you!