Re: (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

[Richard Sharpe <realrichardsharpe () gmail com>]

On Thu, Apr 15, 2021 at 1:23 PM Guy Harris <gharris () sonic net> wrote:
> On Apr 15, 2021, at 2:03 AM, Graham Bloice <graham.bloice () trihedral com> wrote:
>
> > Wireshark is a complicated project to build.  You can follow the tested way, as shown in the Developers Guide, 
> > which is essentially what our Continuous Integration (CI) systems use and most other developers, or you can forge 
> > your own path on less travelled routes strewn with rocks, rusty nails and broken glass that you mostly have to deal 
> > with on your own.
> >
> > Unless you have some inescapable need to do things in a different way, it's easier and more productive to follow 
> > the herd.
>
> Building in a subdirectory with a name other than "build" isn't exactly a "[route] strewn with rocks, rusty nails and 
> broken glass".  *That* should Just Work (at least if the name is all ASCII printable characters and contains no 
> spaces); if it doesn't, that's a sign that the build process isn't robust enough.

Indeed, I routinely build in directories like wireshark-build or
wireshark-<mumble>-build and I have never seen a problem. cmake is not
that silly.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe