Hi Mark, Thanks for the build but its giving me a "MSVCR71D.dll not found" error - I think thats because its a debug build and I dont have Visual Studio installed, any change of a release build?
I'll grab the HDK once there is a release build available and run the tests and let you know. cheers A On 28 June 2010 23:33, Mark Hindess <mark.hind...@googlemail.com> wrote: > > In message <aanlktiluq6e43kgn2ajdia8sfxwocyoeolrsftiyb...@mail.gmail.com>, > Antony Miguel writes: >> >> 32-bit please :) > > http://people.apache.org/~hindessm/win7/ > > These are debug rather than release builds. I'm happy to make release > builds if they are more suited to your requirements. I've only made > java5 artifacts but let me know if you wanted java7. > > It would be useful if you could run the tests and report the results > back. If you get the hdk build and unzip it you can run the tests with: > > ant -f harmony-5.0-hdk-958744/build/test/build.xml > > >> I believe XP->Vista broke with tradition much more Vista->Windows 7 so >> I would imagine if Harmony works on Vista then it would very likely >> work for the vast majority on Windows 7. >> >> As I've said I would suggest that that "it will probably work on >> future versions" should be the default assumption, or at least that >> the version check could be a warning which could be overridden with >> a command line switch? That way you could retain the forced exit if >> you wished but people creating products on top of Harmony would have >> the option to use the command line switch in the knowledge that their >> products would work wherever possible and wouldn't just exit because >> Microsoft had released a new version. > > I don't disagree. This change was easier for now. Assuming the test > results are consistent on windows 7 then accepting dwMajorVersion >= > 6 is probably reasonable. However, until we know if the tests run > correctly on windows 7, allowing versions greater than that doesn't > really make sense. > > Regards, > Mark. > > >
