Wireshark mailing list archives
Re: Wireshark-dev Digest, Vol 121, Issue 2
From: Muhammad Naveez <picspics37 () yahoo com>
Date: Wed, 1 Jun 2016 10:59:28 +0000 (UTC)
i need help in my project "wireshrak plugin in auto car communication.i have dissector problem with doip(diagnoses over intent protocol) protocols. anybody help me its project on GitHub.https://github.com/AMOS-ss16-proj3/amos-ss16-proj3 Thanks From: "wireshark-dev-request () wireshark org" <wireshark-dev-request () wireshark org> To: wireshark-dev () wireshark org Sent: Wednesday, 1 June 2016, 15:53 Subject: Wireshark-dev Digest, Vol 121, Issue 2 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: Copy error during build of copy_cli_dlls (Graham Bloice) 2. Re: Copy error during build of copy_cli_dlls (Paul Offord) ---------------------------------------------------------------------- Message: 1 Date: Wed, 1 Jun 2016 11:19:52 +0100 From: Graham Bloice <graham.bloice () trihedral com> To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] Copy error during build of copy_cli_dlls Message-ID: <CALcKHKpX_xH_6mLeBxnzLTcwcqx6o1Mac1Hy31ZRZZf=9+2F6A () mail gmail com> Content-Type: text/plain; charset="utf-8" On 1 June 2016 at 11:05, Paul Offord <Paul.Offord () advance7 com> wrote:
Hi, I haven?t built Wireshark for a while. I did a fresh git pull and then tried a build. I get a whole raft of errors but they seem to originate from this one: 12>------ Build started: Project: copy_cli_dlls, Configuration: Debug x64 ------ 10> packet-ap1394.c 10> packet-app-pkix-cert.c 10> packet-applemidi.c 10> packet-aprs.c 10> packet-arcnet.c 10> packet-armagetronad.c 10> packet-arp.c 10> packet-artnet.c 10> packet-aruba-adp.c 10> packet-aruba-erm.c 10> packet-aruba-iap.c 10> packet-aruba-papi.c 10> packet-ar_drone.c 10> packet-asap.c 10> packet-ascend.c 12> 0 File(s) copied 10> packet-asf.c 10> packet-assa_r3.c 12> 0 File(s) copied 12> 0 File(s) copied 10> packet-asterix.c 10> packet-at.c 12> 0 File(s) copied 10> packet-atalk.c 12> 0 File(s) copied 10> packet-ath.c 12> 0 File(s) copied 10> packet-atm.c 10> packet-atmtcp.c 12> Error copying file (if different) from "C:/Development/wireshark/wireshark-win64-libs/c-ares-1.9.1-1-win64ws/bin/libcares-2.dll" to "C:/Development/Wireshark/build/run/Debug". I don?t have the directory c-ares-1.9.1-1-win64ws but I do have c-ares-1.11.0-win64ws. I?m building on Windows 7 64-bit with Visual Studio 2013 Community Edition. I run the following command to prep for the build: C:\Development\Wireshark\build>cmake -D ENABLE_CHM_GUIDES=on -G "Visual Studio 12 Win64" ..\ Any advice much appreciated. Best regards?Paul Paul Offord FBCS CITP Chief Technical Officer Advance7
cd .. rd /s /q build mkdir build cmake ... Sometime changes to the build seem to be too much for CMake to handle in an existing build dir and rather than track them down, I've adopted the "take off and nuke the build from orbit" approach. -- Graham Bloice -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.wireshark.org/lists/wireshark-dev/attachments/20160601/db743814/attachment.html> ------------------------------ Message: 2 Date: Wed, 1 Jun 2016 10:53:47 +0000 From: Paul Offord <Paul.Offord () advance7 com> To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] Copy error during build of copy_cli_dlls Message-ID: <69CB24EC39368E438FFE300C1813C50B01A6B5DB@ASLHQSBS.aslhq.local> Content-Type: text/plain; charset="utf-8" Thanks Graham ? that fixed it. Best regards?Paul From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Graham Bloice Sent: 01 June 2016 11:20 To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] Copy error during build of copy_cli_dlls On 1 June 2016 at 11:05, Paul Offord <Paul.Offord () advance7 com<mailto:Paul.Offord () advance7 com>> wrote: Hi, I haven?t built Wireshark for a while. I did a fresh git pull and then tried a build. I get a whole raft of errors but they seem to originate from this one: 12>------ Build started: Project: copy_cli_dlls, Configuration: Debug x64 ------ 10> packet-ap1394.c 10> packet-app-pkix-cert.c 10> packet-applemidi.c 10> packet-aprs.c 10> packet-arcnet.c 10> packet-armagetronad.c 10> packet-arp.c 10> packet-artnet.c 10> packet-aruba-adp.c 10> packet-aruba-erm.c 10> packet-aruba-iap.c 10> packet-aruba-papi.c 10> packet-ar_drone.c 10> packet-asap.c 10> packet-ascend.c 12> 0 File(s) copied 10> packet-asf.c 10> packet-assa_r3.c 12> 0 File(s) copied 12> 0 File(s) copied 10> packet-asterix.c 10> packet-at.c 12> 0 File(s) copied 10> packet-atalk.c 12> 0 File(s) copied 10> packet-ath.c 12> 0 File(s) copied 10> packet-atm.c 10> packet-atmtcp.c 12> Error copying file (if different) from "C:/Development/wireshark/wireshark-win64-libs/c-ares-1.9.1-1-win64ws/bin/libcares-2.dll" to "C:/Development/Wireshark/build/run/Debug". I don?t have the directory c-ares-1.9.1-1-win64ws but I do have c-ares-1.11.0-win64ws. I?m building on Windows 7 64-bit with Visual Studio 2013 Community Edition. I run the following command to prep for the build: C:\Development\Wireshark\build>cmake -D ENABLE_CHM_GUIDES=on -G "Visual Studio 12 Win64" ..\ Any advice much appreciated. Best regards?Paul Paul Offord FBCS CITP Chief Technical Officer Advance7 cd .. rd /s /q build mkdir build cmake ... Sometime changes to the build seem to be too much for CMake to handle in an existing build dir and rather than track them down, I've adopted the "take off and nuke the build from orbit" approach. -- Graham Bloice ______________________________________________________________________ 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 ______________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.wireshark.org/lists/wireshark-dev/attachments/20160601/cfc93297/attachment.html> ------------------------------ _______________________________________________ Wireshark-dev mailing list Wireshark-dev () wireshark org https://wireshark.org/mailman/listinfo/wireshark-dev End of Wireshark-dev Digest, Vol 121, Issue 2 *********************************************
___________________________________________________________________________ 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
Current thread:
- Re: Wireshark-dev Digest, Vol 121, Issue 2 Muhammad Naveez (Jun 01)