W dniu 2017-05-17 o 16:35, Kai Tietz pisze: > 2017-05-17 16:25 GMT+02:00 David Grayson <[email protected]>: >> On Wed, May 17, 2017 at 4:10 AM, Kai Tietz <[email protected]> wrote: >>> The best solution would be something like to include >>> driverspecs.h in specstring.h only, if user intends to use ddk. >> >> Is that how the real DDK works? When you don't have the DDK >> installed, you can still include specstrings.h but it somehow does not >> include driverspecs.h? >> >> --David Grayson > > No idea, and nothing of much interest to us AFAICS. For us, ddk is an > optional component. It isn't mandatory to include it at all. It is > controlled by an configure option to our header's build. > > That means, to rely on driverspecs.h seems to be the wrong thing. > Including it on purpose, if user wants it, sounds something fair. But > to enforce dependency to it in general feels wrong. > > Cheers, > Kai
If user wants driverspecs.h and include it, the problem still exists. There should be no macros '__in' and '__out' for GCC. We could add info to comment about '__in' and '__out' that we recommend '_In_' and '_Out_' in source code instead of '__in' and '__out'. Mateusz > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Mingw-w64-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
