Hi Robert, > Hi Steve, > > I've been taking a look at the Windows build, since I'm keen to use > qpid C++ on that platform.
Great! > I noticed that on trunk the VS project is slightly out of date with > the generated files so it doesn't build (looks like a couple of > generated events had either been renamed or removed?). Hmmm... That happens. > Obviously that was simple to fix, and I've also added a custom build > step (and the spec file) to the project so that a user doesn't have to > run nmake separately from the command line. I originally did this, but removed it during the git-to-svn merge. My thoughts were that since the Qpid release process generates the files, "normal" users won't need to generate them and may not have the ruby/python needed to do it. It's only needed by qpid developers working from svn, so I moved the generate to a separate procedure. I have a Windows-specific install document written as well. Also, even if the generated code is done, there's no way that I've found to bring any new files into the project file. > Are you making any changes to the VS project just now? I'd like to > commit these but I don't want to disrupt anything you're doing. I have some things, yes. Additionally, I've been generating the sln/vcproj files (and that does find all the generated code) so if you check it in, it'll likely show up as much more changed than just what you added. It is not a perfect scheme, and I'm open to suggestion for improvements, but adding the generating step is, I think, worse for non-developers. Let me know what you think. -Steve
