Looks like I made it.
https://github.com/crondaemon/wireshark/runs/490547471?check_suite_focus=true
The artifact can be found in the upper right area of the screen.
On Fri, Mar 6, 2020 at 3:29 PM Dario Lombardo wrote:
>
>
> On Fri, Mar 6, 2020 at 3:21 PM João Valverde <
> joao.valve...@tecnico
On Fri, Mar 6, 2020 at 3:21 PM João Valverde <
joao.valve...@tecnico.ulisboa.pt> wrote:
> If you want to spare some CPU cycles I believe only the user_guide_chm
> target is mandatory for NSIS.
>
> Seems you are missing some dependencies too, asciidoctor and maybe others
> as well.
>
>
Yes to both.
On 06/03/20 13:55, Dario Lombardo wrote:
Si it seems like it is not running the MSVC 2019 command prompt
that takes care of setting the various environment variables.
Well... this is a point. I added the proper action and it made it a
bit further.
https://github.com/crondaemon/wir
>
> Si it seems like it is not running the MSVC 2019 command prompt that takes
> care of setting the various environment variables.
>
Well... this is a point. I added the proper action and it made it a bit
further.
https://github.com/crondaemon/wireshark/runs/490228280?check_suite_focus=true
How
Le ven. 6 mars 2020 à 14:02, Dario Lombardo a écrit :
>
>
> On Fri, Mar 6, 2020 at 12:44 PM Pascal Quantin
> wrote:
>
>>
>>
>> Le ven. 6 mars 2020 à 12:28, Dario Lombardo a écrit :
>>
>>> I am sorry, I still don't understand, I beg your pardon.
>>> You said
>>>
>>> > your machine does not have
For the WiX installer merge module, IIRC CMake will print the "not found"
path if WiX isn't installed. That's been on my cleanup list for some time.
On Fri, 6 Mar 2020 at 06:44, Pascal Quantin wrote:
>
>
> Le ven. 6 mars 2020 à 12:28, Dario Lombardo a écrit :
>
>> I am sorry, I still don't und
On Fri, Mar 6, 2020 at 12:44 PM Pascal Quantin wrote:
>
>
> Le ven. 6 mars 2020 à 12:28, Dario Lombardo a écrit :
>
>> I am sorry, I still don't understand, I beg your pardon.
>> You said
>>
>> > your machine does not have the MSVC redistributable copied in the
>> wireshark-libs folder (as expla
Le ven. 6 mars 2020 à 12:28, Dario Lombardo a écrit :
> I am sorry, I still don't understand, I beg your pardon.
> You said
>
> > your machine does not have the MSVC redistributable copied in the
> wireshark-libs folder (as explained in the developer guide) while it is
> required for the NSIS ins
I am sorry, I still don't understand, I beg your pardon.
You said
> your machine does not have the MSVC redistributable copied in the
wireshark-libs folder (as explained in the developer guide) while it is
required for the NSIS installer.
But I cannot find any point in the developer guide where i
Hi Dario,
Le ven. 6 mars 2020 à 12:16, Dario Lombardo a écrit :
> Hi Pascal
> I'm not sure I got the point. I try to explain what I understand. I have
> one single build, that may have multiple problems, some trivial, some not.
> The error I see in cmake could be ignored, while the one that coun
Hi Pascal
I'm not sure I got the point. I try to explain what I understand. I have
one single build, that may have multiple problems, some trivial, some not.
The error I see in cmake could be ignored, while the one that counts is the
fact I need the MSVC redistributable in the wireshark-lib folder.
Hi Dario,
Le ven. 6 mars 2020 à 11:30, Dario Lombardo a écrit :
> No, it's the same. Have a look at the cmake section and you will see the
> error messages below.
>
Joao is correct: on one side you have a non fatal error in CMake that only
impacts the WiX installer, and in the other side your m
No, it's the same. Have a look at the cmake section and you will see the
error messages below.
On Fri, Mar 6, 2020 at 10:54 AM João Valverde <
joao.valve...@tecnico.ulisboa.pt> wrote:
>
>
> On 06/03/20 08:23, Dario Lombardo wrote:
>
> Example of failing build
>
>
> https://github.com/crondaemon/w
On 06/03/20 08:23, Dario Lombardo wrote:
Example of failing build
https://github.com/crondaemon/wireshark/runs/489648430?check_suite_focus=true
A quick look suggests this is a different build than you indicated
before, for an NSIS package, and the problem seems to be that the
VC_REDIST exe
Maybe this helps?
https://github.com/actions/virtual-environments/issues/195
On 06/03/20 08:07, Dario Lombardo wrote:
Are you saying "set v"? It doesn't print anything.
The installation of VS is pre-made by the github builder itself, not
by me, hence I don't have any control over the installat
Example of failing build
https://github.com/crondaemon/wireshark/runs/489648430?check_suite_focus=true
On Fri, Mar 6, 2020 at 9:07 AM Dario Lombardo wrote:
> Are you saying "set v"? It doesn't print anything.
> The installation of VS is pre-made by the github builder itself, not by
> me, hence
Are you saying "set v"? It doesn't print anything.
The installation of VS is pre-made by the github builder itself, not by me,
hence I don't have any control over the installation options. However I
guess every component is in place, and maybe I just need to add the proper
dir to the PATH. What do
On 3/5/20 2:36 PM, João Valverde wrote:
>
>
> On 05/03/20 15:27, Dario Lombardo wrote:
>> Hi,
>> I'm getting this output from a windows build
>>
>> -- Using VCINSTALLDIR: VCINSTALLDIR-NOTFOUND
>> -- Using MERGE_MODULE_DIR-NOTFOUND\Microsoft_VC142_CRT_x64.msm for the WiX
>> installer
>> -- Config
On 05/03/20 15:27, Dario Lombardo wrote:
Hi,
I'm getting this output from a windows build
-- Using VCINSTALLDIR: VCINSTALLDIR-NOTFOUND
-- Using MERGE_MODULE_DIR-NOTFOUND\Microsoft_VC142_CRT_x64.msm for the
WiX installer
-- Configuring done
-- Generating done
-- Build files have been written
On 3/5/20 7:27 AM, Dario Lombardo wrote:
> Hi,
> I'm getting this output from a windows build
>
> -- Using VCINSTALLDIR: VCINSTALLDIR-NOTFOUND
> -- Using MERGE_MODULE_DIR-NOTFOUND\Microsoft_VC142_CRT_x64.msm for the WiX
> installer
> -- Configuring done
> -- Generating done
> -- Build files have
Hi,
I'm getting this output from a windows build
-- Using VCINSTALLDIR: VCINSTALLDIR-NOTFOUND
-- Using MERGE_MODULE_DIR-NOTFOUND\Microsoft_VC142_CRT_x64.msm for the WiX
installer
-- Configuring done
-- Generating done
-- Build files have been written to: D:/a/wireshark/wireshark/build
What's goin
Hi
The 32bit is not working either. I am not trying to upgrade my Qt version
(although I really can't figure out what the issue should be here for
tshark and wireshark-gtk, and if this is not working, I'll try your debug
scenario.
VS2013 is unfortunately not allowed in our company, not even the C
I seem to remember earlier issues with other folks using VS2012 and wanting
a 64 bit build, due to qt support problems.
VS2013 CE is available for free, you might want to consider that.
As for CMake build instructions did you look at README.cmake in the top
level sources?
When we get CMake total
Hi
I have only VStudio 2012 available here at my workplace. Using CMake 3.0.2,
msvc2012_64_opengl.
The error log (in german) produces the following output:
=
Startet die Generierung des Aktivierungskontextes.
Eingabeparameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBa
On 25 March 2015 at 08:17, Roland Knall wrote:
> Hi
>
> I can build wireshark successfully (gtk and qt interfaces) on Windows, but
> If I want to execute it, he complains that the side-by-side configuration
> is not correct.
>
> If I trace the launch with sxstrace, he complains, that the
> Proces
Hi
I can build wireshark successfully (gtk and qt interfaces) on Windows, but
If I want to execute it, he complains that the side-by-side configuration
is not correct.
If I trace the launch with sxstrace, he complains, that the
ProcessorArchitecture is wrong for the target (amd64).
The build is
26 matches
Mail list logo
