ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Update Windows Build Instructions

From: Stephen Fisher <sfisher@xxxxxxx>
Date: Mon, 5 Jan 2015 16:49:28 -0700
On Mon, Jan 05, 2015 at 03:34:16PM -0500, Ed Beroset wrote:

> Stephen Fisher wrote:
> >Indeed.  So what about making a script to read in Makefile.common and 
> >spitting out those XML files for msbuild?  Or update the msbuild so IDE 
> >things in those files (if any) aren't reset every time its rebuilt.

> It sounds like reinventing a subset of CMake.

> Sorry this sounds like a "sales pitch" -- I've just done this exercise 
> enough times to appreciate that while it's not perfect by a long shot 
> and is maddening when it doesn't work, but even with its flaws, it's 
> better than the alternatives I've found.

I just opened Visual Studio and told it to make a New "Project from 
Existing Code" (and NOT using an external build system).

I know there is a lot more to it because it doesn't know how to link in 
Qt for example, and numerous other issues I'm sure.  But it shows me 
what the .vcxproj file looks like.  It only created one and it includes 
every source file in every directory.  In theory, let's say we finished 
the project file so it could link Qt and build everything just right... 
after that, couldn't changes to Makefile.common just be merged into this 
file with a script?  The source files listed look like this:

 <ClCompile Include="epan\crc8-tvb.c" />

Or am I missing something?