Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Graham Bloice 
On 19 June 2017 at 21:10, Maynard, Chris 
wrote:

> > Sigh. There is something really weird about my cygwin setup. I managed
> to get
> > past the previous problems and now am hitting this:
> >
> >"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
> >"C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
> > (default target) (3) ->
> >"C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
> > (default target) (30) ->
> >"C:\Development\wsbuild64\docbook\user_guide_chm.
> vcxproj.metaproj"
> > (default target) (32) ->
> >"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
> > (default target) (119) ->
> >  CUSTOMBUILD : I/O error : Attempt to load network entity
> > http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> > [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
> >
> > --
> > Regards,
> > Richard Sharpe
> > (何以解憂？唯有杜康。--曹操)
>
> For what it's worth, it might be useful to check the buildbot's
> environment.  For example, if you visit https://buildbot.wireshark.
> org/wireshark-master/waterfall then select the stdio link of the step of
> interest for the most similar buildbot to your system, you can check that
> buildbot's environment and output to see how it compares with your own.
>
> Take Windows Server 2012 R2 x64, Build 3878 for example:
>
> -> ran CMake stdio: https://buildbot.wireshark.
> org/wireshark-master/builders/Windows%20Server%202012%20R2%
> 20x64/builds/3878/steps/compile/logs/stdio
> -> compiled with MSBuild stdio: https://buildbot.wireshark.
> org/wireshark-master/builders/Windows%20Server%202012%20R2%
> 20x64/builds/3878/steps/compile_1/logs/stdio
>
> Hope that helps?  If not, I have a couple of batch files that I use to
> help me set up the environment and to build Wireshark that I could probably
> share?
>
> One last tip to try is to remove Cygwin from your %PATH% prior to running
> cmake.  For me, having Cygwin in the %PATH% causes problems, so I remove it.
> - Chris
>
>
>
+1 for this.  Having Cygwin on the path for Wireshark builds has always
caused problems whenever I've encountered it and I've strongly recommended
folks do NOT do this for a long time.

Another thing to note with CMake builds is that once CMake has located an
external library or function call it will cache that info in CMakeCache.txt
in the build directory and will never "forget" things (even if their path
changes) unless you delete the entry in the file, or delete the file
entirely.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Maynard, Chris 
> Sigh. There is something really weird about my cygwin setup. I managed to get
> past the previous problems and now am hitting this:
> 
>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
> (default target) (3) ->
>"C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
> (default target) (30) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
> (default target) (32) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
> (default target) (119) ->
>  CUSTOMBUILD : I/O error : Attempt to load network entity
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
> 
> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)

For what it's worth, it might be useful to check the buildbot's environment.  
For example, if you visit 
https://buildbot.wireshark.org/wireshark-master/waterfall then select the stdio 
link of the step of interest for the most similar buildbot to your system, you 
can check that buildbot's environment and output to see how it compares with 
your own.

Take Windows Server 2012 R2 x64, Build 3878 for example:

-> ran CMake stdio: 
https://buildbot.wireshark.org/wireshark-master/builders/Windows%20Server%202012%20R2%20x64/builds/3878/steps/compile/logs/stdio
-> compiled with MSBuild stdio: 
https://buildbot.wireshark.org/wireshark-master/builders/Windows%20Server%202012%20R2%20x64/builds/3878/steps/compile_1/logs/stdio

Hope that helps?  If not, I have a couple of batch files that I use to help me 
set up the environment and to build Wireshark that I could probably share?

One last tip to try is to remove Cygwin from your %PATH% prior to running 
cmake.  For me, having Cygwin in the %PATH% causes problems, so I remove it.
- Chris

CONFIDENTIALITY NOTICE: This message is the property of International Game 
Technology PLC and/or its subsidiaries and may contain proprietary, 
confidential or trade secret information.  This message is intended solely for 
the use of the addressee.  If you are not the intended recipient and have 
received this message in error, please delete this message from your system. 
Any unauthorized reading, distribution, copying, or other use of this message 
or its attachments is strictly prohibited.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Richard Sharpe 
On Mon, Jun 19, 2017 at 12:36 PM, Graham Bloice
 wrote:
>
>
> On 19 June 2017 at 19:40, Richard Sharpe 
> wrote:
>>
>> On Mon, Jun 19, 2017 at 11:12 AM, Richard Sharpe
>>  wrote:
>> > On Mon, Jun 19, 2017 at 8:08 AM, Graham Bloice
>> >  wrote:
>> >>
>> >>
>> >> On 19 June 2017 at 15:02, Jeff Morriss 
>> >> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe
>> >>>  wrote:
>> 
>>  Hi folks,
>> 
>>  I am getting this:
>>  
>> 
>> >>> [...]
>> 
>> "C:\Development\wsbuild64\Wireshark.sln" (default target) (1)
>>  ->
>> 
>>  "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
>>  (default target) (62) ->
>> "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
>>  (default target) (116) ->
>>   CUSTOMBUILD : I/O error : Attempt to load network entity
>>  http://docbook.sourceforge.net/release/xsl/current/ht
>> mlhelp/htmlhelp.xsl
>>  [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>>   CUSTOMBUILD : compilation error : file
>>  /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
>>  e
>> lement import
>>  [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>> 
>> >>> [...]
>> 
>>  A quick search suggests that other people are seeing similar errors.
>>  I
>>  definitely have access to the internet and am doing this from home.
>>  Also, a wget from a different shell (cygwin) succeeds for that file.
>> 
>>  Is there some tool I have failed to install that is needed?
>> >>>
>> >>>
>> >>> No tool but you need whatever package supplies `htmlhelp.xsl`.
>> >>>
>> >>> Or you can remove the "--nonet" option which is what is preventing it
>> >>> from
>> >>> trying to get the file off the 'net (there was recently some
>> >>> discussion--but
>> >>> no resolution that I'm aware of--of the wiseness of using "--nonet").
>> >>>
>> >>>
>> >>
>> >> According to the Cygwin package index
>> >>
>> >> (https://cygwin.com/cgi-bin2/package-grep.cgi?grep=htmlhelp.xsl=x86_64)
>> >> that file should be part of the asciidoc package and in my build VM is
>> >> in
>> >> etc/asciidoc/docbook-xsl.
>> >
>> > Thanks for that. I will make sure that I have ascii doc installed. I
>> > extracted the command and ran it manually and initially it seemed that
>> > /etc/xml/catalog was empty, but I managed to copy that from a Linux
>> > system and got further.
>>
>> Sigh. There is something really weird about my cygwin setup. I managed
>> to get past the previous problems and now am hitting this:
>>
>>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>>"C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
>> (default target) (3) ->
>>"C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
>> (default target) (30) ->
>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
>> (default target) (32) ->
>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
>> (default target) (119) ->
>>  CUSTOMBUILD : I/O error : Attempt to load network entity
>> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
>> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>>
>>
>
>
> Have you installed the Cygwin docbook-xml45 package as listed in the
> Developers Guide?
> I think that again, that package wants to reach out to the internet for some
> unknown reason.

Yeah, I installed that after I ran into problems ... any maybe need to
regenerate the cmake files stuff.

> If you're only building Wireshark to run locally you can dispense with the
> docs which does make the build simpler by omitting the
> "-DENABLE_CHM_GUIDES=on" argument to CMake.

I noticed that and have taken that step for the moment.

> If you're aiming to build an installer then you do need to build the docs,
> which requires docbook and it's partners, which just makes life awkward on
> Windows.

Yeah, I will have to sort that out.

> --
> Graham Bloice
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe



-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Graham Bloice 
On 19 June 2017 at 19:40, Richard Sharpe 
wrote:

> On Mon, Jun 19, 2017 at 11:12 AM, Richard Sharpe
>  wrote:
> > On Mon, Jun 19, 2017 at 8:08 AM, Graham Bloice
> >  wrote:
> >>
> >>
> >> On 19 June 2017 at 15:02, Jeff Morriss 
> wrote:
> >>>
> >>>
> >>>
> >>> On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe
> >>>  wrote:
> 
>  Hi folks,
> 
>  I am getting this:
>  
> 
> >>> [...]
> 
> "C:\Development\wsbuild64\Wireshark.sln" (default target) (1)
> ->
> "C:\Development\wsbuild64\docbook\user_guide_chm.
> vcxproj.metaproj"
>  (default target) (62) ->
> "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
>  (default target) (116) ->
>   CUSTOMBUILD : I/O error : Attempt to load network entity
>  http://docbook.sourceforge.net/release/xsl/current/ht
> mlhelp/htmlhelp.xsl
>  [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>   CUSTOMBUILD : compilation error : file
>  /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
>  e
> lement import
>  [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
> 
> >>> [...]
> 
>  A quick search suggests that other people are seeing similar errors. I
>  definitely have access to the internet and am doing this from home.
>  Also, a wget from a different shell (cygwin) succeeds for that file.
> 
>  Is there some tool I have failed to install that is needed?
> >>>
> >>>
> >>> No tool but you need whatever package supplies `htmlhelp.xsl`.
> >>>
> >>> Or you can remove the "--nonet" option which is what is preventing it
> from
> >>> trying to get the file off the 'net (there was recently some
> discussion--but
> >>> no resolution that I'm aware of--of the wiseness of using "--nonet").
> >>>
> >>>
> >>
> >> According to the Cygwin package index
> >> (https://cygwin.com/cgi-bin2/package-grep.cgi?grep=
> htmlhelp.xsl=x86_64)
> >> that file should be part of the asciidoc package and in my build VM is
> in
> >> etc/asciidoc/docbook-xsl.
> >
> > Thanks for that. I will make sure that I have ascii doc installed. I
> > extracted the command and ran it manually and initially it seemed that
> > /etc/xml/catalog was empty, but I managed to copy that from a Linux
> > system and got further.
>
> Sigh. There is something really weird about my cygwin setup. I managed
> to get past the previous problems and now am hitting this:
>
>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
> (default target) (3) ->
>"C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
> (default target) (30) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
> (default target) (32) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
> (default target) (119) ->
>  CUSTOMBUILD : I/O error : Attempt to load network entity
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>
>
>

Have you installed the Cygwin docbook-xml45 package as listed in the
Developers Guide?
I think that again, that package wants to reach out to the internet for
some unknown reason.

If you're only building Wireshark to run locally you can dispense with the
docs which does make the build simpler by omitting the
"-DENABLE_CHM_GUIDES=on" argument to CMake.

If you're aiming to build an installer then you do need to build the docs,
which requires docbook and it's partners, which just makes life awkward on
Windows.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Richard Sharpe 
On Mon, Jun 19, 2017 at 11:12 AM, Richard Sharpe
 wrote:
> On Mon, Jun 19, 2017 at 8:08 AM, Graham Bloice
>  wrote:
>>
>>
>> On 19 June 2017 at 15:02, Jeff Morriss  wrote:
>>>
>>>
>>>
>>> On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe
>>>  wrote:

 Hi folks,

 I am getting this:
 

>>> [...]

"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
 (default target) (62) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
 (default target) (116) ->
  CUSTOMBUILD : I/O error : Attempt to load network entity
 http://docbook.sourceforge.net/release/xsl/current/ht
mlhelp/htmlhelp.xsl
 [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
  CUSTOMBUILD : compilation error : file
 /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
 e
lement import
 [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]

>>> [...]

 A quick search suggests that other people are seeing similar errors. I
 definitely have access to the internet and am doing this from home.
 Also, a wget from a different shell (cygwin) succeeds for that file.

 Is there some tool I have failed to install that is needed?
>>>
>>>
>>> No tool but you need whatever package supplies `htmlhelp.xsl`.
>>>
>>> Or you can remove the "--nonet" option which is what is preventing it from
>>> trying to get the file off the 'net (there was recently some discussion--but
>>> no resolution that I'm aware of--of the wiseness of using "--nonet").
>>>
>>>
>>
>> According to the Cygwin package index
>> (https://cygwin.com/cgi-bin2/package-grep.cgi?grep=htmlhelp.xsl=x86_64)
>> that file should be part of the asciidoc package and in my build VM is in
>> etc/asciidoc/docbook-xsl.
>
> Thanks for that. I will make sure that I have ascii doc installed. I
> extracted the command and ran it manually and initially it seemed that
> /etc/xml/catalog was empty, but I managed to copy that from a Linux
> system and got further.

Sigh. There is something really weird about my cygwin setup. I managed
to get past the previous problems and now am hitting this:

   "C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
   "C:\Development\wsbuild64\docbook\all_guides.vcxproj.metaproj"
(default target) (3) ->
   "C:\Development\wsbuild64\docbook\user_guides.vcxproj.metaproj"
(default target) (30) ->
   "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
(default target) (32) ->
   "C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
(default target) (119) ->
 CUSTOMBUILD : I/O error : Attempt to load network entity
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
[C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Richard Sharpe 
On Mon, Jun 19, 2017 at 8:08 AM, Graham Bloice
 wrote:
>
>
> On 19 June 2017 at 15:02, Jeff Morriss  wrote:
>>
>>
>>
>> On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe
>>  wrote:
>>>
>>> Hi folks,
>>>
>>> I am getting this:
>>> 
>>>
>> [...]
>>>
>>>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
>>> (default target) (62) ->
>>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
>>> (default target) (116) ->
>>>  CUSTOMBUILD : I/O error : Attempt to load network entity
>>> http://docbook.sourceforge.net/release/xsl/current/ht
>>>mlhelp/htmlhelp.xsl
>>> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>>>  CUSTOMBUILD : compilation error : file
>>> /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
>>> e
>>>lement import
>>> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>>>
>> [...]
>>>
>>> A quick search suggests that other people are seeing similar errors. I
>>> definitely have access to the internet and am doing this from home.
>>> Also, a wget from a different shell (cygwin) succeeds for that file.
>>>
>>> Is there some tool I have failed to install that is needed?
>>
>>
>> No tool but you need whatever package supplies `htmlhelp.xsl`.
>>
>> Or you can remove the "--nonet" option which is what is preventing it from
>> trying to get the file off the 'net (there was recently some discussion--but
>> no resolution that I'm aware of--of the wiseness of using "--nonet").
>>
>>
>
> According to the Cygwin package index
> (https://cygwin.com/cgi-bin2/package-grep.cgi?grep=htmlhelp.xsl=x86_64)
> that file should be part of the asciidoc package and in my build VM is in
> etc/asciidoc/docbook-xsl.

Thanks for that. I will make sure that I have ascii doc installed. I
extracted the command and ran it manually and initially it seemed that
/etc/xml/catalog was empty, but I managed to copy that from a Linux
system and got further.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Graham Bloice 
On 19 June 2017 at 15:02, Jeff Morriss  wrote:

>
>
> On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe <
> realrichardsha...@gmail.com> wrote:
>
>> Hi folks,
>>
>> I am getting this:
>> 
>>
>> [...]
>
>>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
>> (default target) (62) ->
>>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
>> (default target) (116) ->
>>  CUSTOMBUILD : I/O error : Attempt to load network entity
>> http://docbook.sourceforge.net/release/xsl/current/ht
>>mlhelp/htmlhelp.xsl
>> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>>  CUSTOMBUILD : compilation error : file
>> /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
>> e
>>lement import [C:\Development\wsbuild64\docb
>> ook\user_guide_chm.vcxproj]
>>
>> [...]
>
>> A quick search suggests that other people are seeing similar errors. I
>> definitely have access to the internet and am doing this from home.
>> Also, a wget from a different shell (cygwin) succeeds for that file.
>>
>> Is there some tool I have failed to install that is needed?
>
>
> No tool but you need whatever package supplies `htmlhelp.xsl`.
>
> Or you can remove the "--nonet" option which is what is preventing it from
> trying to get the file off the 'net (there was recently some
> discussion--but no resolution that I'm aware of--of the wiseness of using
> "--nonet").
>
>
>
According to the Cygwin package index (
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=htmlhelp.xsl=x86_64)
that file should be part of the asciidoc package and in my build VM is in
etc/asciidoc/docbook-xsl.

-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] My Windows build seemed to be going so well until ...

2017-06-19 Thread Jeff Morriss 
On Sun, Jun 18, 2017 at 6:18 PM, Richard Sharpe  wrote:

> Hi folks,
>
> I am getting this:
> 
>
> [...]

>"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj"
> (default target) (62) ->
>"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj"
> (default target) (116) ->
>  CUSTOMBUILD : I/O error : Attempt to load network entity
> http://docbook.sourceforge.net/release/xsl/current/ht
>mlhelp/htmlhelp.xsl
> [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
>  CUSTOMBUILD : compilation error : file
> /cygdrive/c/Development/wireshark/docbook/custom_layer_chm.xsl line 8
> e
>lement import [C:\Development\wsbuild64\docbook\user_guide_chm.
> vcxproj]
>
> [...]

> A quick search suggests that other people are seeing similar errors. I
> definitely have access to the internet and am doing this from home.
> Also, a wget from a different shell (cygwin) succeeds for that file.
>
> Is there some tool I have failed to install that is needed?


No tool but you need whatever package supplies `htmlhelp.xsl`.

Or you can remove the "--nonet" option which is what is preventing it from
trying to get the file off the 'net (there was recently some
discussion--but no resolution that I'm aware of--of the wiseness of using
"--nonet").
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV data types

2017-06-19 Thread Paul Offord 
Or to think of it another way, a feature to allow:

* The merging (enrichment) of network data with other data types - particularly 
attractive in these days of increasing encryption
* Extending the availability of the great features of Wireshark into other 
areas of IT support

Best regards...Paul

-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Jaap Keuter
Sent: 19 June 2017 07:43
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
data types

Hi,

So is this an attempt to make Wireshark into a glorified log file viewer? Kinda 
like Maslow's hammer?

Thanks,
Jaap


> On 19 Jun 2017, at 12:06, Paul Offord  wrote:
> 
>> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
>> logs that are in CSV and TSV format"?
> 
> Yes - I mean arbitrary comma, tab and space separated.  IIS web logs are in 
> Space Separated Variable format (standard W3 format I believe).
> 
>> And is there any reason not to just take the log file reading part of your 
>> code, make it into a libwiretap module that *directly* reads those files 
>> using a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
>> WTAP_ENCAP_IIS_LOG?
> 
> I'm sure it's possible, and that would be a future project.  The code is 
> currently a Win32 Console app written in C++.
> 
>> Note that this would require support for random access to the file when 
>> reading it.
> 
> Yes, and a whole lot more.  I'm going to extend my console app to 
> automatically determine data types, and we would need to replicate this in 
> Wireshark if we are to read the files directly.  I think there will be  whole 
> bunch more challenges, and so you can see that integrating this code into 
> Wireshark is going to be quite a task.
> 
> Going back to the main objective, what I'm proposing is that we enable a 
> PCAP-NG file to contain any text-based data together with a schema - JSON or 
> XML or PCAP-NG proprietary.  There would be one WTAP_ENCAP_xxx type for any 
> text-based data type.  Decoding would be based on the schema data.
> 
> Best regards...Paul
> 
> -Original Message-
> From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On 
> Behalf Of Guy Harris
> Sent: 18 June 2017 23:01
> To: Developer support list for Wireshark 
> Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV 
> and SSV data types
> 
> On Jun 18, 2017, at 5:54 PM, Paul Offord  wrote:
> 
>> Some time ago I wrote a program that reads Microsoft IIS web log files and 
>> converts them into PCAP-NG format.  I then wrote a matching dissector to 
>> produce nice neat output.  I want to rewrite it because:
>> 
>>  • The field names and data types are defined in the first record of the 
>> PCAP-NG file – this is how the dissector knows the layout of the file
>>  • Each data record is encapsulated in a dummy Ethernet frame and I want 
>> to eliminate this
>>  • I’d like to make it more general so that it can also deal with 
>> CSV, TSV and, later, variable format log records
> 
> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
> logs that are in CSV and TSV format"?
> 
> And is there any reason not to just take the log file reading part of your 
> code, make it into a libwiretap module that *directly* reads those files 
> using a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
> WTAP_ENCAP_IIS_LOG?
> 
> Note that this would require support for random access to the file when 
> reading it.
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> 
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 
> __
> 
> This message contains confidential information and is intended only for the 
> individual named. If you are not the named addressee you should not 
> disseminate, distribute or copy this e-mail. Please notify the sender 
> immediately by e-mail if you have received this e-mail by mistake and delete 
> this e-mail from your system.
> 
> Any views or opinions expressed are solely those of the author and do not 
> necessarily represent those of Advance Seven Ltd. E-mail transmission cannot 
> be guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> The sender therefore does not accept liability for any errors or omissions in 
> the contents of this message, which arise as a result of e-mail transmission.
> 
> Advance Seven Ltd. Registered in England

Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV data types

2017-06-19 Thread Jaap Keuter 
Hi,

So is this an attempt to make Wireshark into a glorified log file viewer? Kinda 
like Maslow's hammer?

Thanks,
Jaap


> On 19 Jun 2017, at 12:06, Paul Offord  wrote:
> 
>> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
>> logs that are in CSV and TSV format"?
> 
> Yes - I mean arbitrary comma, tab and space separated.  IIS web logs are in 
> Space Separated Variable format (standard W3 format I believe).
> 
>> And is there any reason not to just take the log file reading part of your 
>> code, make it into a libwiretap module that *directly* reads those files 
>> using a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
>> WTAP_ENCAP_IIS_LOG?
> 
> I'm sure it's possible, and that would be a future project.  The code is 
> currently a Win32 Console app written in C++.
> 
>> Note that this would require support for random access to the file when 
>> reading it.
> 
> Yes, and a whole lot more.  I'm going to extend my console app to 
> automatically determine data types, and we would need to replicate this in 
> Wireshark if we are to read the files directly.  I think there will be  whole 
> bunch more challenges, and so you can see that integrating this code into 
> Wireshark is going to be quite a task.
> 
> Going back to the main objective, what I'm proposing is that we enable a 
> PCAP-NG file to contain any text-based data together with a schema - JSON or 
> XML or PCAP-NG proprietary.  There would be one WTAP_ENCAP_xxx type for any 
> text-based data type.  Decoding would be based on the schema data.
> 
> Best regards...Paul
> 
> -Original Message-
> From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
> Guy Harris
> Sent: 18 June 2017 23:01
> To: Developer support list for Wireshark 
> Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
> data types
> 
> On Jun 18, 2017, at 5:54 PM, Paul Offord  wrote:
> 
>> Some time ago I wrote a program that reads Microsoft IIS web log files and 
>> converts them into PCAP-NG format.  I then wrote a matching dissector to 
>> produce nice neat output.  I want to rewrite it because:
>> 
>>  • The field names and data types are defined in the first record of the 
>> PCAP-NG file – this is how the dissector knows the layout of the file
>>  • Each data record is encapsulated in a dummy Ethernet frame and I want 
>> to eliminate this
>>  • I’d like to make it more general so that it can also deal with CSV, 
>> TSV and, later, variable format log records
> 
> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
> logs that are in CSV and TSV format"?
> 
> And is there any reason not to just take the log file reading part of your 
> code, make it into a libwiretap module that *directly* reads those files 
> using a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
> WTAP_ENCAP_IIS_LOG?
> 
> Note that this would require support for random access to the file when 
> reading it.
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 
> __
> 
> This message contains confidential information and is intended only for the 
> individual named. If you are not the named addressee you should not 
> disseminate, distribute or copy this e-mail. Please notify the sender 
> immediately by e-mail if you have received this e-mail by mistake and delete 
> this e-mail from your system.
> 
> Any views or opinions expressed are solely those of the author and do not 
> necessarily represent those of Advance Seven Ltd. E-mail transmission cannot 
> be guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> The sender therefore does not accept liability for any errors or omissions in 
> the contents of this message, which arise as a result of e-mail transmission.
> 
> Advance Seven Ltd. Registered in England & Wales numbered 2373877 at 
> Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ
> 
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe:

Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV data types

2017-06-19 Thread Paul Offord 
> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
> logs that are in CSV and TSV format"?

Yes - I mean arbitrary comma, tab and space separated.  IIS web logs are in 
Space Separated Variable format (standard W3 format I believe).

> And is there any reason not to just take the log file reading part of your 
> code, make it into a libwiretap module that *directly* reads those files 
> using a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
> WTAP_ENCAP_IIS_LOG?

I'm sure it's possible, and that would be a future project.  The code is 
currently a Win32 Console app written in C++.

> Note that this would require support for random access to the file when 
> reading it.

Yes, and a whole lot more.  I'm going to extend my console app to automatically 
determine data types, and we would need to replicate this in Wireshark if we 
are to read the files directly.  I think there will be  whole bunch more 
challenges, and so you can see that integrating this code into Wireshark is 
going to be quite a task.

Going back to the main objective, what I'm proposing is that we enable a 
PCAP-NG file to contain any text-based data together with a schema - JSON or 
XML or PCAP-NG proprietary.  There would be one WTAP_ENCAP_xxx type for any 
text-based data type.  Decoding would be based on the schema data.

Best regards...Paul

-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Guy Harris
Sent: 18 June 2017 23:01
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
data types

On Jun 18, 2017, at 5:54 PM, Paul Offord  wrote:

> Some time ago I wrote a program that reads Microsoft IIS web log files and 
> converts them into PCAP-NG format.  I then wrote a matching dissector to 
> produce nice neat output.  I want to rewrite it because:
>  
>   • The field names and data types are defined in the first record of the 
> PCAP-NG file – this is how the dissector knows the layout of the file
>   • Each data record is encapsulated in a dummy Ethernet frame and I want 
> to eliminate this
>   • I’d like to make it more general so that it can also deal with CSV, 
> TSV and, later, variable format log records

Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web logs 
that are in CSV and TSV format"?

And is there any reason not to just take the log file reading part of your 
code, make it into a libwiretap module that *directly* reads those files using 
a WTAP_ENCAP_IIS_LOG encapsulation, and write a dissector for 
WTAP_ENCAP_IIS_LOG?

Note that this would require support for random access to the file when reading 
it.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

__

This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be 
guaranteed to be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour 
House, Coopers End Lane, Stansted, Essex CM24 1SJ

__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe