Re: [Valgrind4win-developers] project status

[Chris <cs...@gm...>]

Hi all,

let me add to the topics discussed so far:

1) project status
There are only three developers who made significant contributions to 
this project: TML, Jiri and myself. Sadly I didn't have time in the last 
months to work on this project. The last check-in dates from August 
2012. So yes the project is pretty much idle, but it's definitely not dead.

2) project announcement on various mailing lists or web sites
No problem with that. However it should be made clear that the project 
at this time needs developers only. This means people who want to work 
on the project itself (="developers"), not people who want to use it to 
test their software (="users"). The latter will result in disappointment 
only because the project is just not ready for it.

And BTW I don't want users to build V4W. Whenever there is a V4W 
release, it will be via installer packages just like any other Windows 
software. This saves the users frustration in having to deal with 
setting up a development environment and building the software, and 
frees the developers from assisting users in such tasks.

3) upstream merge
I agree with what has been said. The earliest point when one could think 
about merging the two projects would be the "Alpha" state. However, 
separate development could also continue until a "Beta" or even later 
stage. There is a process how to merge changes from upstream to V4W and 
I can do this whenever necessary.

4) cross-compilation on Linux
This will be significant effort and I don't see a benefit coming from 
this. This is mainly because in order to test any changes you do need 
Windows. So why not build V4W on Windows in the first place? All tools 
required for this are 100% free (MinGW, GCC, autotools, MS SDK, etc.) 
and there is documentation how to set up a development system.

Chris