Re: Apple M1 transition for Wireshark build process

[Roland Knall <rknall () gmail com>]

There are a few issues with M1 still:

A. Not all supporting libraries can be compiled, especially brew supplied
libraries vary deeply.
B. Rosetta and native are nearly par performance wise.
C. Universal binaries would require a real hassle, so I actually would
prefer target-specific ones

In summary, if you run M1s run Rosetta2 atm. Binaries will require a few
months to be stable. If you want to develop though, that can be done
easily, just be aware, that development environment wise you will run into
issues. VSCode does not work yet 100%, Qt you must compile yourself,
QtCreator does not work at all for me so far, ...

I can give you pointers in the next Dev Den Meeting if you want

Cheers
Roland

chuck c <bubbasnmp () gmail com> schrieb am Sa. 28. Nov. 2020 um 16:42:

> This question was about getting a pre-compiled binary:
>
> https://ask.wireshark.org/question/20092/which-version-should-i-download-on-new-mac-pro-with-new-m1-chip/
>
> but the bigger question is how does the transition to M1 affect developers?
>
> Is it possible to get a new M1 machine and build for both processor
> architectures?
> Does it matter for most code changes?
>
> I think Roland mentioned on the developers den he had been working on
> compiling on the new chip.
> Are there enough gotchas that are worth a Wiki page/update to dev
> guide/open issue to track?
>
> thanks
> chuckc
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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