There is general support for dropping autotools on master (after fixing the
rpm build).
But I'll rewrite the patches for 2.4 and 2.6 to add a compile switch, so
that the patch only applies if it is build with cmake. Adding Objective-C
builds to auto tools seems pointless at this point, to me at
I'm trying to submit some edits to the WSDG. I'm testing them against the
HTML version.
If I change on of the source asciidocs and execute:
C:\development\wsbuild64>*msbuild docbook\developer_guide_html.vcxproj*
Only developer-guide.xml gets rebuilt.
If I make another change to the same file
Den tis 10 apr. 2018 03:50Guy Harris skrev:
> On Apr 9, 2018, at 8:44 AM, Wireshark code review <
> code-review-do-not-re...@wireshark.org> wrote:
>
> > URL:
> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=d347091da962a3bb095c62339fc6faa07d189a9f
> >
On Apr 9, 2018, at 8:44 AM, Wireshark code review
wrote:
> URL:
> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=d347091da962a3bb095c62339fc6faa07d189a9f
> Submitter: Roland Knall (rkn...@gmail.com)
> Changed: branch: master
>
On Apr 9, 2018, at 11:58 AM, Maynard, Chris wrote:
> Maybe there’s a way to detect whether /Qspectre is supported by the compiler
> or not and omit it if it isn’t in order to avoid all of these warnings?
check_c_compiler_flag(-Qspectre C__Qspectre_VALID)
For Win32/64 developers, the Wireshark Developer's Guide currently mentions
"Microsoft Visual Studio 2015 Community Edition" as the compiler to download
and install[1]. That is the version I'm currently running. Here are the
relevant details:
Microsoft Visual Studio Community 2015