CMake Build System #3
Conversation
librabbitmq and example/amqp_sendstring can be build under linux now.
- By default look in the CMAKE_SOURCE_DIR/rabbitmq-codegen, then CMAKE_SOURCE_DIR/../rabbitmq-codegen unless RABBITMQ_CODEGEN_DIR is set - If FETCH_CODEGEN_FROM_GIT use the CMake ExternalProject to do it
Did not enable because it requires popt and cmake needs to know how to the popt headers and library
Utilities in the tools/ directory will now be built if the popt library is found
|
With workarounds for those three issues, I've built under Linux, Visual Studio 10 and mingw/msys, and it looks good. It will be great to have a proper visual studio build. |
Codegen.py should be copied to the bin directory and not the source directory.
stdint.h is provided by MinGW/MSYS on Win32. It is not provided by MSVC
|
The only other thing I can think of at this point is the ability for the user to choose whether to build a shared or static library. Right now it unconditionally creates a shared library. |
|
I'm happy to merge without support for building static libs. Static libs might be nice, but I guess support for them can easily be added later on. |
|
Ok. Go ahead an merge away! |
|
Merged. Because the changes had to go through our hg repo, the git commit IDs have changed in the merge process. (I can sometimes get the commit IDs to round-trip through hg and stay the same, but in this case some commits had distinct authors and committers which hg doesn't understand.) |
Created a cmake-based build system.
The benefit being it can be built just as easily on Windows (MSVC, MinGW), Linux and Mac.
First time sending a pull request to you, let me know if I should be going through a different channel.