Hi Carl, > Steve Huston wrote: > >> Here is the latest release candidate for M4: > >> > >> http://people.apache.org/~rhs/qpid-M4-RC6/ > >> > > > > -1 > > > > Windows build fails in the broker - there were more changes to > > generated files between RC5 and 6 - these break the Windows build > > since the Visual Studio projects must be regenerated to match the > > changes to generated C++ files. > > it their a way we can script this or generate these sections of the > project files, so they automajically stay in sync
I've tried to come up with a more foolproof way to handle this. Visual C++'s make can't deal with including outside files (like the generated .mk files). It also doesn't have wildcards. MS Build can handle this, I believe, but unless/until VC++ migrates, that option is not available. I use a tool called MPC (MakefileProjectCreator: http://ociweb.com/products/mpc) to generate the files locally, after running the C++ code generator. It's possible for the release process to run MPC and generate the files. The problem here is that it would change a version-controlled artifact during release, which makes control tough. Also, I imagine making Windows users obtain and run MPC (which requires Perl) is a non-starter. -Steve
