Hello. Should the RC2 build work on Windows w/o any changes? I tried it on Win8 / VS 2011 and got a warning from cmake and VS errors in the build process. I wasn't going to bother reporting them until I saw the below note about win7 and vs2008. If it *should* work on Windows, I'll follow-up with more details about my issues (but didn't want to get in the way if that's not a part of 0.4).
Thanks, Paul On Wed, Feb 20, 2013 at 4:57 PM, Cliff Jansen <cliffjan...@gmail.com> wrote: > Looks good. Build and ctest success on rhel6 64 bit. > > Successful build and expected ctest results on Windows 7 and VS2008. > > Cliff > > On Wed, Feb 20, 2013 at 3:31 PM, Rafael Schloming <r...@alum.mit.edu> > wrote: > > Source posted here: > > - http://people.apache.org/~rhs/qpid-proton-0.4rc2/ > > > > Java binaries here: > > - > https://repository.apache.org/content/repositories/orgapacheqpid-280/ > > > > I'd like to call an official vote soon, e.g. tomorrow, so please have a > > look and share your results here. > > > > Changes from RC1: > > > > PROTON-199: support python 2.4 > > PROTON-236 freegetopt compat for proton-c windows builds. > > PROTON-243: fixed LIB_SUFFIX magic > > PROTON-200: maintain a minimum credit level for each receive link > > PROTON-200: make similar changes to Java MessengerImpl > > PROTON-200: allow recv(-1) to grant unlimited credit > > PROTON-232: described arrays seem to force the descriptor to be of the > same > > type as the array Fixed bug in code.c pn_data_encode_node: was always > using > > the parent->type for everything inside an array, including the > descriptor. > > PROTON-242: Shared library used JNI code has poor name > "libproton-swig.so" > > Shared library now has name libproton-jni.so i.e. follows the naming > > conventions of its companion jar. > > PROTON-217: cmake build system should include install target for Java > > binaries > > > > --Rafael >
