The "official" 2.2.x releases are built with Qt 5.6.1.
On 27 December 2016 at 14:48, Anders Broman
wrote:
> Hi,
>
> FWIW I think what I was referring to was around this issue
> https://www.wireshark.org/lists/wireshark-dev/201406/msg00021.html and it
> may have been an nmake build…
>
>
>
> Yes I
Traditionally, Bugzilla hasn't had very strong antispam measures. This has
become a major issue for some public installations. For example, the Eclipse
project now requires explicit permission for new users to open bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1306750
We've been getting sp
Well, you are… It’s a community thing, where lots of input is collected and
made available to the public.
So go browse through the resources and find a place where you feel you can
contribute.
Enjoy.
> On 26 Dec 2016, at 14:53, Jonathan Mator wrote:
>
> I want to be part of this organizatio
Hi,
FWIW I think what I was referring to was around this issue
https://www.wireshark.org/lists/wireshark-dev/201406/msg00021.html and it may
have been an nmake build...
Yes I think I saw someone claiming to build with Qt 5.7. I haven't tried...
Regards
Anders
From: wireshark-dev-boun...@wiresha
Hi Anders,
I plan to upgrade Qt but I thought I'd try a build with releases I've used
before. I notice that the Qt site is offering 5.7 - is that a supported
release?
Thanks...Paul
Sent from Samsung Mobile on O2
Original message
From: Anders Broman
Date:27/12/2016 14:04 (
@Paul - I would also recommend to update to the latest version, but at
least 5.6. I am currently building with 5.6.1 on all three plattforms.
regards
Roland
On Tue, Dec 27, 2016 at 3:03 PM, Anders Broman
wrote:
> Hi,
>
> At some point I think there was a fault in Qt causing it to not copy all
>
Hi,
At some point I think there was a fault in Qt causing it to not copy all .dll
when running the command to do so. I'm currently building with Qt 5.6 which I
believe is supposed
To be LTS.
Regards
Anders
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On
I'm building the latest Wireshark source on Windows 7 with QT5.5.1 and VS 2013.
As you may have seen from earlier posts, I scratched my old build environment
and I'm creating a new one. The build prep and build (Debug) complete
successfully, but when I try to start Wireshark I get a message sa
I deleted the source and build directories, and then did a fresh git clone.
Build prep ran fine and I've just run a successful build.
Bets regards...Paul
From: Paul Offord
Sent: 26 December 2016 21:50
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Build with VS 2013 on W
It is break/fail from 2 or 3 month
You can merge
Le mar. 27 déc. 2016 à 12:41, Dario Lombardo
a écrit :
> What do you suggest, then? Wait for backporting or merge?
>
>
>
>
>
> On Tue, Dec 27, 2016 at 12:28 PM, Alexis La Goutte <
> alexis.lagou...@gmail.com> wrote:
>
> Hi Dario,
>
> It is comin
What do you suggest, then? Wait for backporting or merge?
On Tue, Dec 27, 2016 at 12:28 PM, Alexis La Goutte <
alexis.lagou...@gmail.com> wrote:
> Hi Dario,
>
> It is coming from some patch not (yet) backport to master-2.2 (after
> upgrade to PD Ubuntu 16.04)
>
> (It is why i search to disable so
Hi Dario,
It is coming from some patch not (yet) backport to master-2.2 (after
upgrade to PD Ubuntu 16.04)
(It is why i search to disable some steps for some branch)
Cheers
On Tue, Dec 27, 2016 at 10:49 AM, Dario Lombardo <
dario.lombardo...@gmail.com> wrote:
> Hi,
> I'm backporting this chang
Hi,
I'm backporting this change to master-2.2
https://code.wireshark.org/review/#/c/19433/
but the ubuntu PD buildbot fails because of some lintian checks that seem
not to be related to my change
https://buildbot.wireshark.org/petri-dish/builders/Ubuntu%20x86-64%20Petri%20Dish/builds/9642/steps/
13 matches
Mail list logo