From: Pete B. <pb...@gm...> - 2011-02-04 10:18:56
|
On 2011.02.04 05:42, Graeme Gill wrote: > I don't agree with this. In my code, I don't think I've got a single > #ifdef with regard to MSVC vs. MinGW. The only change is the build > tool config. We don't have #ifdef for MinGW in libusb either (I think we used to have one, which we removed easily). But I've seen quite a few instances where I wrote code in MSVC that needed fixing or modification in MinGW. Of course, as I said, the goal of the MinGW is to be very close to the MS native API, and they are doing a pretty good job, so most of the stuff we get are warnings rather then breakage. Are you using gcc with the same options libusb uses? If you use -Wshadow, you're gonna get a warning as soon as you use an "index" variable for instance, and I can definitely see our contributors using index or one of the other shadowed variable. And we're also stricter with our gcc options compared to MSVC, so we tend to pick stuff that MSVC lets slide. What options do you use when compiling with MinGW? Regards, /Pete |