Re: mDNSResponder build errors on Windows

Subject: Re: mDNSResponder build errors on Windows

From: Tom Otvos <email@hidden>

Date: Fri, 10 Jun 2005 11:32:17 -0400

Delivered-to: email@hidden

User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Title: Message

Don,

Yes, thanks. I did manage to get a build of almost all the components by explicitly having the Platform SDK headers searched *after* the stock headers. This is ordinarily not the way to use the Platform SDK, but it works for now. I also noted that in the project settings for the mDNSResponder service, there is an explicit path reference to "C:\Program Files\Microsoft Platform SDK for Windows XP SP2\Include", presumably to allow it to find the missing netfw.h. Since that version of the Platform SDK doesn't exist anymore, I don't think that should be there, but changing that path to any subsequent Platform SDK would probably also work.

While it is unimportant to me, the PrinterSetupWizard continues to fail building. Now that I know there are some explicit system header paths in some project settings, I see that it is looking for "C:\WINDDK\2600.1106\inc" and "C:\WINDDK\2600.1106\inc\wxp", in order to resolve tcpxcv.h, so you need to have the Driver Development Kit installed too. And, for completeness, a quick scan of all the projects in the solution indicates that these two projects are the only ones that explicitly hard code system header paths.

Hopefully this will help other experimenters.

-- Tom Otvos

"Don't think you are. Know you are." - Morpheus

Don Messerli wrote:

If the platform SDK and Visual Studio includes are in separate directories, you may want to reverse the order that Visual Studio searches the include directories.

-----Original Message-----
From: bonjour-dev-bounces+don=email@hidden [mailto:bonjour-dev-bounces+don=email@hidden] On Behalf Of Tom Otvos
Sent: Friday, June 10, 2005 9:05 AM
To: email@hidden
Subject: mDNSResponder build errors on Windows

I have just downloaded the mDNSResponder source, and am trying the build the whole solution using Visual Studio.NET. Using the stock Visual Studio installation, I was getting compiler errors when the source was trying to find netfw.h. Googling this problem suggested a solution that involved using the most recent Platform SDK, but when I try to compile with that, then I get a mountain of other warnings and errors, such as:

c:\Development\Microsoft Platform SDK\Include\WSPiApi.h(44) : error C2894: templates cannot be declared to have 'C' linkage
c:\Development\Bonjour SDK\mDNSResponder-107.1\mDNSShared\dnssd_ipc.h(93) : warning C4005: 'MSG_WAITALL' : macro redefinition

So, my question is: what Visual Studio and Platform SDK combination is required to get this solution to compile cleanly? I am sure I can mix and match my headers to try and coax this to work, but someone somewhere must have gotten this to compile so I am hoping there might be a simple answer.

Thanks in advance.

--
-- Tom Otvos

"Don't think you are. Know you are." - Morpheus

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bonjour-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bonjour-dev/email@hidden This email sent to email@hidden