The current windows command-line build depends on a copy of MSVC, which users may prefer as it's the "official" compiler/linker for Windows..
There's also the third option of getting the Eclipse CDT to generate and manage our builds. I have almost no experience with CDT and I've no idea if that pre-reqs MSVC or similar, but I believe Pete and Sebastien have used it. Cheers Andy On 9/4/06, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
The dependence on MSVC struck me as odd for an open source project when I first saw it but I was reluctant to try to alter something that basically works. I don't think going to the Express Edition helps much since we would still be dependent on a Microsoft product - even if it is free. I think it is better to provide a command line build (as we already do on Linux) as the definitive way to build the product and then anyone who wants to can adapt their favourite IDE to work with that. So I vote for option 2. On 04/09/06, Simon Laws <[EMAIL PROTECTED]> wrote: > > Having just raised a patch to create a VC7 build for BigBank I'm taking a > step back and thinking that we need a better position on Windows builds as > we have too many variations. In particular I just tried to open the VC7 > Calculator sample project and it's not compatible with my oldish verision > of > VC7. So we are faced with even more varieties of project files. This is > not > sensible. I have two proposals. > > 1/ For those who want to use MSVC lets agree a version that we support and > try and stick with that. Can I suggest Microsoft Visual C++ 2005 Express > Edition. I have to admit that I haven't tried this but I will move if we > agree this is the right direction to be going in. Has anyone tried it? > > 2/ Implement a command line build for windows so that we can automate the > build process. I am currently looking at a cygwin build based on the *nix > project automake files. I haven't got it working just yet but will report > back. > > Thoughts? > > Simon > >
