Re: [Ggnfs-devel] Decisions for the Visual Studio build projects

[Brian G. <br...@gl...>]

Jason Papadopoulos wrote:
> I think I'm set for now. The pol51opt Murphy rating code still
> uses global variables, but these are fairly well insulated from
> the rest of the codebase. Turning them into another structure
> should be easy, but enough changes have piled up that I wanted
> to commit what I have first.
> 
> Brian, sorry for the churn in src/exprimental, I promise this
> will be the last big upheaval.

Hello Jason and Colleagues.

It's no problem Jason since I was expecting some early upheaval until 
the code settles down.

For the moment I have added two new VS build projects, pol51m0bx and 
pol51optx, for the new code whilst leaving pol51m0b and pol51opt intact 
for the old code.

Beyond this, however, there are some decisions that we need to take for 
the Visual Studio build projects depending on how many people still want 
to use ggnfs with Visual Studio.

Firstly, as I am now using Visual Studio 2008 (VC++ v9), I have added a 
vc9 build directory to the build.vc directory.  This is the _only_ VC++ 
build system that I am now maintaining.  Hence, unless someone else is 
maintaining the vc7 and vc8 build projects, these will now be out of 
date and will not fully compile ggnfs.  And, of course, they will get 
worse with time.

So do we need to maintain the vc7 and vc8 build systems for ggnfs?  And, 
if we do, who is going to be able to do this?

If they are not being maintained, my view is that we should remove them 
since they will mislead people into thinking that they work when this is 
not the case.

   best regards,

       Brian Gladman