Stephen Warren wrote: > It looks like we don't need to ship setupapi.h at all. > > I deleted this file from libconcord, made sure I had the Microsoft > Platform SDK installed, opened the .sln file using MS Visual Studio 2005 > Express, adjusted the include paths to point at the platform SDK, and > everything builds just fine. > > By my understanding, development on Windows pretty much always requires > both a C compiler and a platform SDK installation, so this shouldn't be > anything new to people building apps from source on Windows. > > So, it seems we can remove setupapi.h from CVS, and add notes to > INSTALL.windows that the platform SDK is required. > > Marco: Do you agree?
If Marco can confirm your findings, I'll nuke it. The less code we have to distribute that's not ours, the happier I'll be. -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
