Wireshark mailing list archives

Re: CMake on Windows - Can build, but not run executable


From: Graham Bloice <graham.bloice () trihedral com>
Date: Thu, 26 Mar 2015 13:19:00 +0000

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 totally sorted, I'll update the Developers Guide to use
that rather than nmake.  Still some things to do yet.


On 26 March 2015 at 13:10, Roland Knall <rknall () gmail com> wrote:

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
CultureFallBacks = de-DE;de
ManifestPath = C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe
AssemblyDirectory = C:\dev\Wireshark\cmakebuild\run\
Application Config File =
-----------------
INFORMATION: Manifestdatei
"C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe" wird analysiert.
INFORMATION: Die Manifestsdefinitionsidentität ist "(null)".
FEHLER: Zeile 8: Der Wert  des "processorArchitecture"-Attributs im
assemblyIdentity-Element ist ungültig.
FEHLER: Bei der Generierung des Aktivierungskontextes ist ein Fehler
aufgetreten.
Beendet die Generierung des Aktivierungskontextes.


I am trying to build with 32bit now, and will keep you updated. I've
figured it may have something to do with Qt, and the fact, that the package
for opensource is only supporting 64 bit with VStudio2013. Why tshark and
wireshark-gtk are affected by this, I can't really figure out.

Btw, should there be another page on the wiki for building with cmake on
Windows? Running the setup script was one thing, but the main thing with my
devenv.bat was, that I used to set WIRESHARK_BASE_DIR, but with that I
never got the build running. As soon as I set WIRESHARK_LIB_DIR as
environment variable, the build worked. I used the stdio information from
the buildbot to figure it out, but others may well have some issues here.

regards,
Roland

On Wed, Mar 25, 2015 at 6:32 PM, Graham Bloice <
graham.bloice () trihedral com> wrote:

On 25 March 2015 at 08:17, Roland Knall <rknall () gmail com> 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
ProcessorArchitecture is wrong for the target (amd64).

The build is a Windows 64bit build



Using VS2013, CMake 3.1.3, QT 5.4.1 msvc2013_64_opengl.

I don't normally build x64, so gave it a go using the x64 native compiler
and CMake fails configure, the testing for various sizes fails as CMake is
asking the linker to use both x64 and x86 modes??

If I use the cross compiler (i.e. x86 building x64) then CMake does
configure and the resulting build runs for me (both qt and gtk).

I usually run depends (http://www.dependencywalker.com/) to check what
DLL's etc are to be loaded.


--
Graham Bloice


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://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://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org
?subject=unsubscribe




-- 
Graham Bloice
Software Developer
Trihedral UK Limited
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: