keLists.txt:
# XXX Add a dependency on ${_ws_lib_dir}/current_tag.txt?
That would somehow force a run of win-setup.ps1 to be part of the build
step. The tricky part is sequencing it so that it would be the first
target to be built.
--
Graham Bloice
_
On 22 April 2016 at 15:48, Evan Huus wrote:
> On Fri, Apr 22, 2016 at 10:24 AM, Jeff Morriss
> wrote:
> >
> >
> > On Fri, Apr 22, 2016 at 3:28 AM, Graham Bloice <
> graham.blo...@trihedral.com>
> > wrote:
> >>
> >> Just thinking for
On 21 April 2016 at 18:31, Jeff Morriss wrote:
>
>
> On Thu, Apr 21, 2016 at 8:15 AM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>>
>> The latest update to the change no longer checks .l files, so no errors
>> are produced now, just warnings
On 20 April 2016 at 03:29, Jeff Morriss wrote:
> On 04/19/2016 05:17 AM, Graham Bloice wrote:
>
>>
>> On 18 April 2016 at 22:48, Guy Harris > <mailto:g...@alum.mit.edu>> wrote:
>>
>> On Apr 18, 2016, at 2:16 PM, Graham Bloice
>> m
ev mailing list
>>>> Archives: https://www.wireshark.org/lists/wireshark-dev
>>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>>> mailto:wireshark-dev-requ...@wireshark.org
>>>> ?subject=unsubscribe
>>>>
&g
On 18 April 2016 at 22:48, Guy Harris wrote:
> On Apr 18, 2016, at 2:16 PM, Graham Bloice
> wrote:
>
> > What should we do about the lex files? Guy's last comment on this issue
> was
> >
> > Some "generated" code is "generated" by copyin
" by copying it from the
> .l/.lemon/.y/etc. files; the problem is that we'd like to check that
> code, but not code that's actually *generated*.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing lis
On 14 April 2016 at 11:01, Graham Bloice
wrote:
>
>
> On 14 April 2016 at 01:07, Yang Luo wrote:
>
>> Hi Graham,
>>
>> On Thu, Apr 14, 2016 at 12:50 AM, Graham Bloice <
>> graham.blo...@trihedral.com> wrote:
>>
>>>
>>>
rk.org/review/gitweb?p=wireshark.git;a=blob;f=epan/dissectors/packet-ssl.c
>
>
I think the TLS client extension stuff is in packet-ssl-utils.c, in
function ssl_dissect_hnd_hello_ext().
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob;f=epan/dissec
On 14 April 2016 at 01:07, Yang Luo wrote:
> Hi Graham,
>
> On Thu, Apr 14, 2016 at 12:50 AM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>>
>>
>> On 13 April 2016 at 17:26, Yang Luo wrote:
>>
>>> Hi Graham,
>>>
>
t;
>
>
> Have a nice day
>
> GV
>
>
>
>
>
Hi Gianluca,
We haven't changed what happens at all with wpcap.dll. I guess we'll have
to just make a big jump to current libpcap and create another patch to fix
what hurts, although I know Guy was keen
On 13 April 2016 at 17:26, Yang Luo wrote:
> Hi Graham,
>
> On Wed, Apr 13, 2016 at 6:11 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>>
>>
>> On 13 April 2016 at 06:07, Yang Luo wrote:
>>
>>> Hi Guy,
>>>
>>
S2015 Update 1 has
totally broken driver remote deploy and test. I need to check if Update 2
has fixed that.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-
On 12 April 2016 at 18:51, Alexis La Goutte
wrote:
>
>
> On Tue, Apr 12, 2016 at 2:30 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>> In case someone has spare time on their hands, a question on Ask
>> Wireshark (
>> https://ask.wireshar
/wsug_html_chunked/ChCustProtocolDissectionSection.html
).
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options
to see 802.11 control and management packets in Wireshark (also
> encrypted
> 802.11 data packets, you need to specify thedecipher key in Wireshark in
> order to decrypt those packets), otherwise you will only see 802.11 data
> packets.
>
> Switching on the *Monitor Mode* will disconnec
On 11 April 2016 at 19:37, Guy Harris wrote:
> On Apr 11, 2016, at 7:29 AM, Jeff Morriss
> wrote:
>
> > On Sun, Apr 10, 2016 at 4:44 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
> >
> >> After creating an initial change to add checkAPI t
On 11 April 2016 at 16:54, Jeff Morriss wrote:
>
>
> On Mon, Apr 11, 2016 at 11:36 AM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>>
>>
>> On 11 April 2016 at 16:03, Jeff Morriss
>> wrote:
>>
>>>
>>>
>>>
On 11 April 2016 at 16:03, Jeff Morriss wrote:
>
>
> On Mon, Apr 11, 2016 at 10:29 AM, Jeff Morriss
> wrote:
>
>>
>> On Sun, Apr 10, 2016 at 4:44 PM, Graham Bloice <
>> graham.blo...@trihedral.com> wrote:
>>
>>> After creating an initial cha
-x86-petri-dish\build\cmbuild\wsutil\checkAPI_wsutil.vcxproj]
--
Graham Bloice
Running checkAPI_capchild-base
Running checkAPI_capchild-todo
Running checkAPI_caputils-base
Running checkAPI_caputils-todo
Running checkAPI_codecs
Running checkAPI_crypt
CUSTOMBUILD : warning : Found
o build a Wireshark installer.
>
> I can't find those projects.
>
> Thanks,
>
> Juanjo Martin
>
>
Nope, they should be in the top-level of your build directory. Do you have
NSIS installed? Did CMake find it (look in the CMakeCache.
> Does anybody have any resource/idea/instructions that can help me?
>
> Thanks,
> Juanjo Martin
>
>
At present we don't support that scenario. You have to provide a full
build environment and compile your plugin there.
--
Graham Bloice
__
\ui\text_import.c(1031): error
> C2065: 'scanner': undeclared identifier
> [C:\Development\wsbuild64\ui\ui.vcxproj]
>
> But dfilter is built with lemon isn't it? Flex is Cygwin 2.5.39-1 and
> there's not any newer version available...
>
On Windows, using CMake
On 30 March 2016 at 18:10, João Valverde
wrote:
>
>
> On 30-03-2016 16:46, Graham Bloice wrote:
>
>>
>>
>> On 30 March 2016 at 16:02, João Valverde
>> > <mailto:joao.valve...@tecnico.ulisboa.pt>> wrote:
>>
>>
>>
>> O
time to do that personally, but if someone does want to
submit a change to temporarily add nmake build instructions until the
deprecation date, I suggest that the appropriate place is a README.nmake in
the top-level of the sources.
--
Graham Bloice
_
manual
configuration in config.nmake you should be able to return to nmake quite
easily.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscrib
On 30 March 2016 at 16:02, João Valverde
wrote:
>
>
> On 30-03-2016 14:57, Graham Bloice wrote:
>
>>
>>
>> On 30 March 2016 at 14:39, João Valverde
>> > <mailto:joao.valve...@tecnico.ulisboa.pt>> wrote:
>>
>>
>>
>> No p
a custom WIRESHARK_VERSION_EXTRA of "-GMB"
shows up as you would like it to, so I'm not sure why yours should be
different. Maybe this has been caused by your change of git and the old
(broken) version.h is lying around in your build directory. Whenever you
change fundamental things, I&
On 30 March 2016 at 14:39, João Valverde
wrote:
>
>
> On 30-03-2016 14:25, João Valverde wrote:
>
>>
>>
>> On 30-03-2016 14:20, João Valverde wrote:
>>
>>>
>>>
>>> On 30-03-2016 08:48, Graham Bloice wrote:
>>>
>>>
.
>
The plan is that nmake will be left in the 2.0 branch, but removed from
master and 2.2.
If anyone wishes to retain nmake builds then they can locally create a
branch from the last master revision before the deletion of nmake and then
keep that branch in s
- Looking for inet_aton - not found
>> -- Looking for inet_ntop
>> -- Looking for inet_ntop - not found
>> -- Looking for inet_pton
>> -- Looking for inet_pton - not found
>> -- Looking for issetugid
>> -- Looking for issetugid - not found
>> -- Looking for mkdtemp
opriate Visual
Studio batch startup file. If it's not being set, then you aren't setting
up your build command shell correctly.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https:/
ing for 64-bit off_t - present with _fseeki64
> -- Checking for fseeko/ftello
> --
> -- The following OPTIONAL packages have been found:
>
> * AIRPCAP
> * CARES
> * GCRYPT (required version >= 1.4.2)
> * GEOIP
> * GMODULE2
> * GNUTLS (required version >= 2.12
ark/zlib
> -- ZLIB libs: zlib
> -- C-Flags: /DWIN32 /D_WINDOWS /W3
> -- CXX-Flags: /DWIN32 /D_WINDOWS /W3 /GR /EHsc
> -- Warnings as errors: /WX
> -- Check if the system is big endian
> -- Searching 16 bit integer
> CMake Error at C:/Program Files
> (x86)/CMake/s
-requ...@wireshark.org?subject=unsubscribe
>>
>
I'm a little surprised that VS2015 worked straight away, have you built an
installer and tested that? I thought there might be issues with the split
C runtime library in VS2015.
I still build with VS2013 on Win 7 (in a VirtualBox VM
are likely down to missing some required Cygwin
packages, probably Text/asciidoc and Text/docbook-xml45.
The other errors seem to be a bad reference to gmodule-2.0.lib when
attempting to link wsutil and a bad reference to krb5.h when compiling
packet-kerberos.c.
Can you post the complete output o
ters used inside the .cpp files, but
> the UTF8_HORIZONTAL_ELLIPSIS is most often used.
>
> --
> Thomas
>
>
Windows users of tshark have a similar issue with UTF-8 entities for the
left and right arrows, e.g. 64850â┼'http(80), I
tbucket\wsbuild32\docbook\generate_developer-guide.xml.vcxproj.metaproj"
> (default targets) -- FAILED.
> 43>Done Building Project
> "C:\Users\robcra01\Documents\WiresharkBitbucket\wsbuild32\docbook\release_notes_html.vcxproj.metaproj"
> (default targets) -- FAILED.
> 2
far as I know).
>
>
The VC++ compiler support for Unicode can be found at
https://msdn.microsoft.com/en-us/library/xwy0e8f2(v=vs.120).aspx, this is
for VS2013, our current compiler of choice.
For UTF-8 encoded strings, there has to be a BOM in the source file.
--
Graham Bloice
_
On 16 March 2016 at 09:42, Alexis La Goutte
wrote:
>
>
> On Wed, Mar 16, 2016 at 10:25 AM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>> Gerald,
>>
>> Slightly related, is there any chance of improving the message associated
>> with a ch
mailing list
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
--
Gra
gt;>
>>> echo Adding Environment Vars for Wireshark-Qt ...
>>> set CYGWIN=nodosfilewarning
>>> set WIRESHARK_BASE_DIR=D:\Development
>>> set WIRESHARK_TARGET_PLATFORM=win64
>>> set QT5_BASE_DIR=D:\Development\Qt5.5\5.5\msvc2013_64
>>> set WIRE
ed.
>>
>> Is it possible to compile Wireshark for win10 machines or did I just make
>> a simple mistake, which I haven't notieced yet?
>>
>> Regards
>>
>> T. Scholz
>>
>>
>> ---
>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüf
",
> "zlib-devel" and "zlib0" v1.2.8.3 are installed.
>
> Is it possible to compile Wireshark for win10 machines or did I just make
> a simple mistake, which I haven't notieced yet?
>
>
>
I haven't personally compiled on Win 10 yet, but I c
safe_Dissection", with the HEAD at the last
patch submitted.
Make changes, git commit --amend to retain the commit message with its
Change-Id then git-review to submit it to Gerrit.
I don't normally submit with "git-review -f" so the branch is left around
until it's merged wi
On 9 March 2016 at 18:06, Richard Sharpe
wrote:
> Hi folks,
>
> Need to review some stuff. Where/what are the instructions?
>
>
https://wiki.wireshark.org/Development/SubmittingPatches
--
Graham Bloice
_
urrently they are green, although I'm getting a build error on Windows
about generation of the AUTHORS file. The binaries are all still good
though.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archiv
ledge, doesn't have dissectors for malware so is
unlikely to have their signatures in the binaries.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
ing nmake, then
epan\Makefile.common is probably the right spot. More ifnormation on your
changes would help.
As other have said we'll need to see the output from the build step to help
further.
--
Graham Bloice
___
o submit a change for this.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
anges?
>>
>
> cd asn1\lte-rrc
> msbuild /m /p:Configuration=RelWithDebInfo
> generate_dissector-lte-rrc.vcxproj
> cd ..\..
> msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln
>
> Regards,
> Pascal.
>
>
This info deserves a spot in the Developers Guide.
On 17 February 2016 at 15:32, Anders Broman
wrote:
> Hi,
>
> The files in the extcap folder are no longer built with nmake...
>
> Regards
>
> Anders
>
All part of the plan to get you to move to CMak
dows native Python directory (e.g.
C:\Python27) and the Python scripts directory (e.g. C:\Python27\Scripts) on
my path, the latter for git-review.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:
a special output message, which would help you, or should I just
> post all the errors messages in here?
>
>
>
>
>
Post them as an attachment and I'll have a quick scan. I don't have many
spare cycles to do
VS2010 is, that I wanted to
> check, whether I can use my old environment.
>
>
>
> I will now work with VS2013, since building has worked.
>
>
>
>
>
It would be nice to know if it is a simple issue that can be fixed, or if
it's terminal and the Developers Guide sh
ed/ChSetupWin32.html#ChSetupPrepareCommandCom)
?
> When I try to start compilation with the command “msbuild /m
> /p:Configuration=RelWithDebInfo Wireshark.sln”, I get a lot of warnings and
> errors.
>
A small sample of the errors may be helpful to diagnose what's wrong,
howev
that to anyone
else. This build of WinPcap was only done to bring the build environment
up to date, there were no other functional changes in WinPcap.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:
;\wsbuild64\docbook\developer_guide_docbook.vcxproj]
>
> 0 Warning(s)
> 3 Error(s)
>
> Does someone have had the same problem?
>
>
You've likely failed to install the Cywin packages for AsciiDoc and
DocbookXML. See this section of the Developers Guid
e following OPTIONAL packages have been found:
>
> * AIRPCAP
> * CARES
> * GCRYPT (required version >= 1.4.2)
> * GEOIP
> * GMODULE2
> * GNUTLS (required version >= 2.12.0)
> * GTK2
> * HtmlViewer
> * KERBEROS
> * LUA
> * PCAP
> * POD
> * P
r (old-style formal list?) (C:\Developmen
> t\wireshark\ui\qt\wlan_statistics_dialog.cpp) [C:\Development\wsbuild64\
> ui\qt\qtui.vcxproj]
>C:\Qt\5.5\msvc2013_64\include\QtWidgets/qsizepolicy.h(155): error C205
> 9: syntax error : '}' (C:\Development\wireshark\ui\qt
target_properties(target PROPERTY OUTPUT_NAME
newname).
It might be possible to add a collection of set_target_property() calls in
CMakeCustomLists.txt which can be used to add custom CMake modifications.
Currently a custom file is permitted at the top-level and in asn1, epan and
ui\gtk.
Dealing with dir
On 2 January 2016 at 21:21, Thomas Wiens wrote:
> On 02.01.2016 21:40 Graham Bloice wrote:
>
> > What version of Git do you have? In your case it looks like git bash is
> > being called and isn't able to execute tools\runlex.sh.
> >
> > I have git version 2.6.
On 2 January 2016 at 20:03, Thomas Wiens wrote:
> On 02.01.2016 20:15 Graham Bloice wrote:
>
> > You're definitely missing the asciidoc\docbook bits. See the bottom of
> the
> > packages list for the Cygwin part of the setup (
> >
> https://www.wireshark.org/
On 2 January 2016 at 17:41, Thomas Wiens wrote:
> On 02.01.2016 18:06 Graham Bloice wrote:
>
> > Can you try:
> >
> > msbuild /p:Configuration=RelWithDebInfo /t:clean
> > .\docbook\user_guide_docbook.vcxproj
> >
> > to clean the user guide docboo
On 2 January 2016 at 16:48, Thomas Wiens wrote:
> On 02.01.2016 17:23 Graham Bloice wrote:
>
> > I can't see what the error is from so little context. You're using the
> > same build approach, i.e. CMake and the same environment with VS2010 and
> > that work
On 2 January 2016 at 14:15, Thomas Wiens wrote:
> On 02.01.2016 13:38 Graham Bloice wrote:
>
> > Out of interest, what are the reasons for sticking with MSVC2010?
>
> Never change a running system.
>
> I've got VC2013 installed under Win64, but the build proce
re built with, MSVC2013. Any plugin development that is meant to be
installed along with the production version should also use MSVC2013.
Out of interest, what are the reasons for sticking with MSVC2010?
--
Graham Bloice
___
Sent
ows API
than the regular Desktop API that Wireshark uses.
The "official" Qt supported platforms are listed here:
http://doc.qt.io/QtSupportedPlatforms/index.html, notably Win 10 isn't on
the list, but as Pascal
ill not possible?
>
Qt 5.6.x will have builds for VS2015. There are betas available at
http://download.qt.io/development_releases/qt/5.6/5.6.0-beta/. I'm not
aware of anyone working on this for Wireshark yet.
--
Graham Bloice
On 31 December 2015 at 11:35, Bálint Réczey wrote:
> 2015-12-31 0:10 GMT+01:00 Anders Broman :
> >
> > Den 30 dec 2015 17:01 skrev "Graham Bloice" >:
> >>
> >>
> >>
> >> On 30 December 2015 at 10:52, VIKRAM VENKATESH HEGDE
> &
shark.sln"
$Global:doprep = "msbuild /m /p:Configuration=RelWithDebInfo
nsis_package_prep.vcxproj"
$Global:dopackage = "msbuild /m /p:Configuration=RelWithDebInfo
nsis_package.vcxproj"
Note that the "Import-VisualStudioVars" command comes from PowerShell
Community E
> lost when GTK is removed. But in my opinion we could integrate the GTK
> version
>
> First and worry about the GUI part later. If it’s possible to add the
> feature as a series of smaller patches that would make the review easier
> rather than
>
> A humongous
automated build area (
https://www.wireshark.org/download/automated/) that is closest to the
sources you are using to compare load times.
The releases are built using the same method as you're using.
--
Graham Bloice
___
so have no advice to offer.
I suggest you continue without the luxury of git-review for the moment.
Googling for Gerrit push over https found this link:
https://www.mediawiki.org/wiki/Gerrit/Tutorial#Push_using_HTTPS, not sure
if that's relevant though.
--
Graham Bloice
__
rsion of ssh, e.g. in C:\Python27\Lib\site-packages\git_review\cmd.py, in
function query_reviews_over_ssh, modify the path to ssh in the
run_command_exc() call to be r"\C:\Program Files\git\usr\bin\ssh.exe".
This might need adjusting for your paths.
You can use Gerrit without git-rev
sion),
git-review version (git-review --version) and do you have ssh.exe from
path\to\git\usr\bin on the path (where.exe ssh.exe)?
Are you running a Windows native python, what version of python?
--
Graham Bloice
___
Sen
://wiki.wireshark.org/Development/SubmittingPatches
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-
On 25 November 2015 at 22:54, Guy Harris wrote:
>
> On Nov 25, 2015, at 12:02 PM, Alexis La Goutte
> wrote:
>
> > On Wed, Nov 25, 2015 at 8:17 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
> >
> >> There is no current auto-install for Qt. A
On 25 November 2015 at 20:02, Alexis La Goutte
wrote:
>
>
> On Wed, Nov 25, 2015 at 8:17 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>> I have plans to create a chocolatey "meta-package" such as
>> wireshark-build-essentials t
nt via:Wireshark-dev mailing list
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
--
Graham Bloice
Software D
On 20 November 2015 at 09:51, Dario Lombardo
wrote:
>
> On Thu, Nov 19, 2015 at 5:59 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>> There's also the:
>>
>> 2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall
>>
t; Sorry if it's a stupid question, but I like to understand all the code
>> audit tools that run around wireshark.
>> Thanks.
>> Dario.
>>
>
--
Graham Bloice
___
Sent via:Wires
ef to ipproto_val_ext, and then
used that in the plugin.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/optio
cal changes, edit away.
If you want to push those changes back to Wireshark so you don't have to
apply your local change every time you update your sources then submit a
change (https://wiki.wireshark.org/Development/Submit
to);
See ws_symbol_export.h for the details.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wiresha
Will it work again?
>
> Thanks,
> Martin
>
A typo in the URL, should be:
https://www.wireshark.org/download/automated/src/
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark
omething is crashing in a dumpcap test on the 2.0 buildbot but not on the
> trunk buildbot.
>
> Does anybody know what program is crashing and, if it's one of our
> programs, what the stack trace is?
>
I can't replicate that on my Win 7 x86 build, I've run the
#cmakdefine for HAVE_IO_H.
What's the best way to make this all consistent, fix CMake and the _WIN32
guards to use HAVE_IO_H, or change the docs and ascend_scanner to use
_WIN32?
--
Graham Bloice
___
Sent via:Wi
tingPatches/GitForWindows).
Note that the latest git installers for Windows might have not put their
copy of ssh on your path, so when calling it directly you might have to
prefix it with the path, e.g. "C:\Program Files\Git\usr\bin\ssh.exe" -p ...
--
Graham Bloice
_
developers can sanely even begin to handle the
volume of submissions.
A Bugzilla entry with a capture illustrating the issue is always handy for
verifying the changes.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Ar
ke -f Makefile.nmake verify_tools
> fails
> with a file win32.mak not found error. So I guess I'm looking at the wrong
> instructions.
>
> Can someone point me at how to build 2.0 for Windows.
>
> Thanks
>
> Andy Ling
>
>
>
--
Graham Bloice
;> dumpcap -i ssh://sshhost:ssh -A user:strongpassword -w
>> /tmp/sshhost-capture.pcap
>>
>> What still WIP:
>> - manual
>> - autotools
>> - nmake
>>
>> Comments, suggestions, ideas appreciated. I'd suggest to give specific
>> code co
p>cl var.c
Microsoft (R) C/C++ Optimizing Compiler Version 18.00.31101 for x86
Copyright (C) Microsoft Corporation. All rights reserved.
var.c
Microsoft (R) Incremental Linker Version 12.00.31101.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:var.exe
var.obj
c:\temp>.\va
;)
>
> I watched in moc_main_windows.cpp to be sure that my slot was here but it
> is not. therefore i think there is a problem here but i don't know how to
> resolve this one.
>
> thanks for your help
>
>
--
Graham Bloice
__
I ran across this, it's about propagating licence info among a chain of
software projects.
http://spdx.org/about-spdx
Is it something we should look at?
--
Graham Bloice
___
Sent via:Wireshark-dev mailing
m interesting on doing it in Linux.
>
> Thanks in advance.
>
> Juanjo Martin
>
>
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
at you mostly managed yourself. This
> was very courageous :)
> I fully agree with you: we should remove proto_tree_add_text before 2.0
> lands, otherwise it might start polluting the dissectors again.
>
> Cheers,
> Pascal.
>
Well done Michael, I agree with Pascal, 2.0 is the righ
Is there a sub group that will look info
> PMIPv6 related dissector changes?
>
One of the core developers will have a look when time permits. It also
helps to raise an entry on the Wireshark bugzilla and attach a capture that
contains the protocol in qu
look at conversations in README.dissector,
especially conversation_add_proto_data and conversation_get_proto_data.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wir
s://www.wireshark.org/docs/man-pages/) but I'm not sure if that's
1.12.x or 1.99.x.
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscrib
301 - 400 of 999 matches
Mail list logo
