[Wireshark-dev] Is there a way to disable documentation generation?

2017-07-31 Thread Michael Lum
Is there a way to disable the documentation generation? The 2.4.0 source will not build for me under Windows 7, cmake 3.8.2 set WIRESHARK_BASE_DIR=C:\ws240-64 REM REM Note if you want to change this AFTER you have built: REM Do 'clean', then 'prep', then 'build', 'package' REM set W

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Graham Bloice
On 31 July 2017 at 23:06, Michael Lum wrote: > Is there a way to disable the documentation generation? > > The 2.4.0 source will not build for me under Windows 7, cmake 3.8.2 > > > set WIRESHARK_BASE_DIR=C:\ws240-64 > > REM > REM Note if you want to change this AFTER you have built: > REM

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Graham Bloice
On 1 August 2017 at 14:15, Graham Bloice wrote: > > > On 31 July 2017 at 23:06, Michael Lum > wrote: > >> Is there a way to disable the documentation generation? >> >> The 2.4.0 source will not build for me under Windows 7, cmake 3.8.2 >> >> >> set WIRESHARK_BASE_DIR=C:\ws240-64 >> >> REM >>

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Michael Lum
ehalf Of Graham Bloice Sent: August-01-17 6:42 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? On 1 August 2017 at 14:15, Graham Bloice mailto:graham.blo...@trihedral.com>> wrote: On 31 July 2017 at 23:06, Mi

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Graham Bloice
he first? > > -- > *From:* Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] *On > Behalf Of *Graham Bloice > *Sent:* August-01-17 6:42 AM > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] Is there a way to dis

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Michael Lum
1-17 10:44 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? On 1 August 2017 at 18:10, Michael Lum mailto:michael@starsolutions.com>> wrote: Hi Graham, thanks for the help. I wasn't sure if you wa

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Michael Lum
h or does it take care of \ /? From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Michael Lum Sent: August-01-17 11:16 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? Th

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Michael Lum
Behalf Of Michael Lum Sent: August-01-17 1:44 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? I added some "message" output to the FindASCII script: -- CYGWIN_INSTALL_PATH=c:\cygwin64 -- l_a2x_ex=c:/cygwin64/bin

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-01 Thread Michael Lum
-boun...@wireshark.org] On Behalf Of Michael Lum Sent: August-01-17 1:47 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? This is from my 2.2.5 build with the same "message" calls added: -- CYGWIN_INSTALL_P

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-02 Thread Graham Bloice
ark-dev [mailto:wireshark-dev-boun...@wireshark.org] *On > Behalf Of *Michael Lum > *Sent:* August-01-17 1:47 PM > > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] Is there a way to disable documentation > generation? > > This is from my 2.2.5 bu

Re: [Wireshark-dev] Is there a way to disable documentation generation?

2017-08-02 Thread Michael Lum
Bloice Sent: August-02-17 3:30 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Is there a way to disable documentation generation? Michael, I've never run into this issue as I have (always) had Cygwin in C:\Cygwin. Interestingly, the build slaves (