Re: Wireshark-dev Digest, Vol 106, Issue 43

[Phool Chand Azad <phoolchandazad () gmail com>]

hi
  i am going to use tscc-v5.10 as wireshark compiler. serial no of my
product is 63A9F0EA7BB98050796B649E85481845 .
 so
    how  can i retrieve license key of it.
     i am using following website....

     http://www.protomatics.com/tsnc_install_unix.html


Thank you

On Thu, Mar 26, 2015 at 6:49 PM, <wireshark-dev-request () wireshark org>
wrote:

> Send Wireshark-dev mailing list submissions to
>         wireshark-dev () wireshark org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://wireshark.org/mailman/listinfo/wireshark-dev
> or, via email, send a message with subject or body 'help' to
>         wireshark-dev-request () wireshark org
>
> You can reach the person managing the list at
>         wireshark-dev-owner () wireshark org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wireshark-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Supported Python versions? (B?lint R?czey)
>    2. Re: CMake on Windows - Can build, but not run executable
>       (Roland Knall)
>    3. Re: CMake on Windows - Can build, but not run executable
>       (Graham Bloice)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 26 Mar 2015 13:18:04 +0100
> From: B?lint R?czey <balint () balintreczey hu>
> To: Developer support list for Wireshark <wireshark-dev () wireshark org>
> Subject: Re: [Wireshark-dev] Supported Python versions?
> Message-ID:
>         <
> CAK0OdpxJr0rQT-qB+8dfvCV3Cg4tbE3ZJ9CSVXz+ZLPVfeh6LQ () mail gmail com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi Peter,
>
> 2015-03-24 18:17 GMT+01:00 Peter Wu <peter () lekensteyn nl>:
> > On Sun, Mar 22, 2015 at 04:58:14PM +0100, Pascal Quantin wrote:
> > > 2015-03-22 16:48 GMT+01:00 Peter Wu <peter () lekensteyn nl>:
> > >
> > > > Hi,
> > > >
> > > > Triggered by a build error due to html2text.py, I have recently
> started
> > > > with adding Python 3 support to various Python scripts[1][2]. The
> change
> > > > to html2text.py[1] was tested with Python 2.6, 2.7, 3.2 and 3.4.
> > > >
> > > > The configure script however checks for Python >= 2.5 which was first
> > > > released in 2006 with the last security update in 2011. This version
> > > > also lacks support for nice language constructs such as 'with'.
> > > > checklicenses.py is already incompatible with this.
> > > >
> > > > Any objections if this gets bumped to 2.6 or even 2.7? The
> > > > dfilter-test.py script already requires 2.7 (or newer).
> > >
> > > Hi Peter,
> > >
> > > the OSX 10.5 x86 buildbot still runs Python 2.5, so bumping the minimum
> > > Python  version would require updating the buildbot. So it's better to
> keep
> > > compatibility for the scripts used during build steps.
> > >
> > > Pascal.
> >
> > According to the ComputerWorld source listed by Wikipedia[1], OS X 10.5
> > became unsupported since June 2011. Python 2.5 also does not receive
> > security updates anymore. (OS X 10.6 has Python 2.7 which is still
> > supported.)
> Since we use Python with verified input and only for building
> Wireshark the security concerns don't apply here.
> Otherwise I think it would be OK to move to newer Python version.
>
> Cheers,
> Balint
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 26 Mar 2015 14:10:59 +0100
> From: Roland Knall <rknall () gmail com>
> To: Developer support list for Wireshark <wireshark-dev () wireshark org>
> Subject: Re: [Wireshark-dev] CMake on Windows - Can build,      but not run
>         executable
> Message-ID:
>         <
> CAFyRefmMxppRuAZ9r_jebqNtUBL5x2qsHYu_D3HXe+BS6Gd8YQ () mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://www.wireshark.org/lists/wireshark-dev/attachments/20150326/bad5f007/attachment.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 26 Mar 2015 13:19:00 +0000
> From: Graham Bloice <graham.bloice () trihedral com>
> To: Developer support list for Wireshark <wireshark-dev () wireshark org>
> Subject: Re: [Wireshark-dev] CMake on Windows - Can build,      but not run
>         executable
> Message-ID:
>         <
> CALcKHKrmL4rfJsmffO_e3mqUUMhURp1_HeJ9UVLrerBB9sC-1A () mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://www.wireshark.org/lists/wireshark-dev/attachments/20150326/305bfd7e/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev () wireshark org
> https://wireshark.org/mailman/listinfo/wireshark-dev
>
>
> End of Wireshark-dev Digest, Vol 106, Issue 43
> **********************************************
___________________________________________________________________________
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