Re: Removal of Visual Studio solution and project files

[mmann78 () netscape net]

I guess I like the overall setup of the solution file and the ability to jump between tshark and Wireshark easily 
without opening new files.  I don't believe the "setup Windows development" steps (which I thought were very good) 
mention supporting building Wireshark through the solution file, it was just something I stumbled upon and was happy 
was there.  I'm familiar enough with VS that I could tell from day 1 that it wouldn't build Wireshark, but that was 
okay with me.  Making the solution file work for building has always been a desire of mine, but it's very low on the 
list (I'm much better at C than I am with build configurations, and it's not like there's anything wrong with the 
command line)



-----Original Message-----
From: Graham Bloice <graham.bloice () trihedral com>
To: Developer support list for Wireshark <wireshark-dev () wireshark org>
Sent: Wed, Sep 18, 2013 5:07 am
Subject: Re: [Wireshark-dev] Removal of Visual Studio solution and project files


On 17 September 2013 22:51, Pascal Quantin <pascal.quantin () gmail com> wrote:


          
    
Hi Michael,
      
      why not load directly the executable in Visual as described here:      http://wiki.wireshark.org/Development/Tips 
? It works pretty well      and does not require an obsolete project file.
      

      Le 17/09/2013 23:45, mmann78 () netscape net a écrit :
    

    
        
-1 from me.  It's my debugger of choice.  While an          integrated solution would be better, I'm okay with the 
current          project files.  The default solution is nice to add the          dissectors/files you're working 
on/consistently modify for          quick reference.  Outside of the debugger, I realize it is          just a 
glorified text editor, but I'm okay with that.
        
 





The method Pascal describes is always the one I use if debug Wireshark using Visual Studio, although I normally prefer 
WinDbg. Having an out of date solution file doesn't seem to me to improve debugging in any way at all.


If the CMake build on Windows stuff ever comes to fruition, then Visual Studio users will have a much easier task of 
building and modifying Wireshark in an environment they're used to, although any new files will have to be added to the 
CMakeLists.txt rather than the solutions\projects CMake produces.


Personally I think that if the files are to remain, they should be maintained.  If they aren't maintained they should 
go.




___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe