Skip to content

wireshark.mpb: Out-of-source options made OS generic#48

Merged
mitza-oci merged 2 commits intoDOCGroup:masterfrom
iguessthislldo:master
Jan 19, 2018
Merged

wireshark.mpb: Out-of-source options made OS generic#48
mitza-oci merged 2 commits intoDOCGroup:masterfrom
iguessthislldo:master

Conversation

@iguessthislldo
Copy link
Copy Markdown
Member

In order to support macOS Wireshark builds, I changed wireshark.mpb to use two features, wireshark in source build and wireshark_cmake for out of source builds using CMake. The structure is mostly the same otherwise, but the library location can't default based on the build location anymore.

@jwillemsen
Copy link
Copy Markdown
Member

Can't we just use wireshark and on Windows use the paths? Don't like that there is a special MPC feature for this

@iguessthislldo
Copy link
Copy Markdown
Member Author

This only effects Windows and macOS, where the extra parameters are necessary if you use Cmake as part of the Wireshark build. wireshark should still work like it's always worked on Linux and any other platform that has autoconf. Could you elaborate on the MPC feature?

@mitza-oci
Copy link
Copy Markdown
Member

Wireshark 2.x is sufficiently different from 1.x that we will need some kind of MPC feature to indicate the difference. As we've done our testing it's become clear that wireshark.mpb must take into account which of wireshark's two different build methods are used.

https://www.wireshark.org/docs/wsdg_html/#ChToolsGCC

Wireshark’s build environment can be configured using CMake on Windows and either CMake or Autotools on Linux, macOS, and UNIX. CMake is designed to support out of tree builds. So much so, that in tree builds do not work properly in all cases.

So the CMake build method is also possible on Linux (perhaps even preferred for consistency, maybe they will drop autotools). Now instead of having the user set the MPC feature wireshark2, the user sets wireshark_cmake.

Comment thread ChangeLog Outdated
* config/wireshark.mpb:
* config/global.features:

When using Wireshark builds built using Autoconf (like Linux),
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tabs -> spaces here

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's strange since I wrote this in vim set to 4 spaces for tabs.

Comment thread config/wireshark.mpb Outdated
// Autoconf / In Source Wireshark Build Method
// This one is how the Wireshark Developers Guide says to build Wireshark on
// Linux (autogen.sh).
// This is also used for older 1.x Wireshark Windows builds.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... and Wireshark 2 when installed by a Linux package manager

Comment thread config/wireshark.mpb
// WIRESHARK_BUILD
// The location of the build that the user choose when building Wireshark.
// It must contain the config.h file after building Wireshark.
// WIRESHARK_LIB
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since these libraries are always under WIRESHARK_BUILD, should we make it so that WIRESHARK_LIB is just the relative path?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants