Interesting question. Using STL as-is was a challenge in itself with the WDK. I have not ventured beyond.
I can give this a try. Remember, the WDK has it's own compiler which is not the same as your VS2005/VS2008 complier (check the version numbers). It is highly likely there are a few bugs here and there.
Interesting question. Using STL as-is was a challenge in itself with the WDK. I have not ventured beyond.
I can give this a try. Remember, the WDK has it's own compiler which is not the same as your VS2005/VS2008 complier (check the version numbers). It is highly likely there are a few bugs here and there.
Note, that USE_MSVCRT=1 and USE_STL=1 didn't gel well (at least for WDK 6001).
Thanks for sharing your experience. I tried using USE_LIBCMT=1 instead of msvcrt, but problems remained. Given that even STL is problematic, I'm going have to reconsider using the WDK.
– ski Apr 6 '09 at 0:12 We build our app part w/ VS200x and the driver only with the WDK. Note, the ddkbuild utility is just a wrapper batch file over the commandline arguments (I use it all the time) and it probably won't help sort out compiler issues. – dirkgently Apr 6 '09 at 3:56 I suggested to use ddkbuild for building driver and using standard vs project to build the application.
You will have a solution that one of the projects (driver) will be build with custom build using ddkbuild and second one (Boost) will be build standard way. – Ilya Apr 6 '09 at 11:31.
Boost may already include a work-around for your issues, but isn't applying it because it doesn't recognise the compiler you're using (probably because drivers rarely use boost). Try examining (and possibly editing) boost/config/select_compiler_config. Hpp and boost/config/compiler/visualc.
Hpp to make sure the compiler workarounds for MSVC are enabled.
I would suggest going different way, i. E compiling driver from VS200. X using this (ddkbuild) nice tool.
Being myself a command line person and using makefiles everywhere possible, I find build utility not useful for complex project. There is tons of limitation within MS build utility and I would recommend using VS environment for compiling your project. I'm not sure if there is a howto in the ddkbuild, but it's straight forward to integrate ddkbuild.
Bat into VS custom build option.
Thanks, I'll probably go this route. – ski Apr 6 '09 at 0:14 1 IMMHO, The ddkbuild is of little help when you have a compile error. – dirkgently Apr 6 '09 at 3:57 I'm not 100% sure but I think it's possible to display errors and warnings in the VS log, but any way it's same as using build from command line you need to open log files to see the errors.
– Ilya Apr 6 '09 at 11:32 @Ilya: By default, it displays the output as it'd with any custom build tool. However, you won't get the 'click to go to erroneous line' functionality or a grouping of errors etc. If you are willing to go that extra mile, yes, even that is possible. – dirkgently Apr 6 '09 at 13:20 If you are choose not going that extra mile (like me:) ), you still in better position than a pure command line build, i.
E the situation is not worse with driver and much better with user mode application. – Ilya Apr 6 '09 at 13:56.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.