Having the build directory under the source tree is still considered an
out-of-source build and is generally convenient and customary.
Having the support libraries path under the source tree is bad practice
however and the root cause for your errors, as already mentioned by others.
On
On May 4, 2023, at 10:16 AM,
wrote:
> Succeeded by -- creating C:\Project\wireshark, cloning in to
> C:\Project\wireshark\wireshark, making C:\Project\wireshark\build, and
> running CMake from within C:\Project\wireshark\build
>
> My build directory was also a peer, but not named ‘build’,
Succeeded by -- creating C:\Project\wireshark, cloning in to
C:\Project\wireshark\wireshark, making C:\Project\wireshark\build, and running
CMake from within C:\Project\wireshark\build
My build directory was also a peer, but not named ‘build’, and not under
C:\Project\wireshark. How odd.
Try setting WIRESHARK_BASE_DIR to C:\Project
Notice in section 2.2.11 at
https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWindows that
WIRESHARK_BASE_DIR is the *parent* directory of where the git clone
happened.
Gilbert
On Wed, May 3, 2023 at 9:10 PM wrote:
> The issues with building
It is preferred, that WIRESHARK_BASE_DIR is defined at the top directory,
and not underneath the source directory. Also, it cannot be omitted as
documented in our build documentation. Additionally, it is recommended to
do an out-of-source build, to better be able to update the sources if
needed.
The issues with building from a git clone are:
1. I clone into C:\Project\wireshark. The make adds libraries to
C:\Project\wireshark\wireshark-win64-libs and then complains at the end that
targets contain paths that are prefixed in the source directory.
2. I want to use
