Minor changes.

I've rearranged some code, pulling the frame processing code to a seperate function. This removes 2 indentation steps and hopefully makes things easier to understand. Logic was not changed.

The alignment issue is actually very easy to fix. Qt provides a function to parse byte data into numbers fixing its endian format.

Also, on UNIX, unit tests do not run because library is not found without either setting rpath or LD_LIBRARY_PATH. Since it's only unit tests, rpath is good enough.

On Fri, Sep 12, 2014 at 12:27:17PM -0700, Matt Broadstone wrote:
>    In src/qamqpclient.cpp:
>  > -        } else {
>  > -            break;
>  > -        }
>  > -    }
>  > +    while (processAvailableFrame());

>    can you actually just move the code back into readReady and wrap it in a
>    forever { }? I don't see the need to move it to a wholly separate function
>    if nothing else is going on, it seems this just reduces the indentation
>    level by one so is simply aesthetic

I find it less readable when there is a sudden "break". But yes, that
could be fixed by 

 if (socket->bytesAvailable() < readSize)
    break/return;


The positive of splitting the function out is that now it does what
you expect it should do (based on function name). And since it's
dealing with 1 frame at a time, it's easier to understand. When I
initially looked at the original function, I found it confusing what
it actually was trying to do.

I can move it back if that's not a good enough reason.

- Adam