It's like JSON but smaller and faster.
MessagePack is an efficient binary serialization format, which lets you exchange data among multiple languages like JSON, except that it's faster and smaller. Small integers are encoded into a single byte and short strings require only one extra byte in addition to the strings themselves.
#include <msgpack.hpp>
#include <string>
#include <iostream>
#include <sstream>
int main()
{
msgpack::type::tuple<int, bool, std::string> src(1, true, "example");
// serialize the object into the buffer.
// any classes that implements write(const char*,size_t) can be a buffer.
std::stringstream buffer;
msgpack::pack(buffer, src);
// send the buffer ...
buffer.seekg(0);
// deserialize the buffer into msgpack::object instance.
std::string str(buffer.str());
msgpack::object_handle oh =
msgpack::unpack(str.data(), str.size());
// deserialized object is valid during the msgpack::object_handle instance is alive.
msgpack::object deserialized = oh.get();
// msgpack::object supports ostream.
std::cout << deserialized << std::endl;
// convert msgpack::object instance into the original type.
// if the type is mismatched, it throws msgpack::type_error exception.
msgpack::type::tuple<int, bool, std::string> dst;
deserialized.convert(dst);
// or create the new instance
msgpack::type::tuple<int, bool, std::string> dst2 =
deserialized.as<msgpack::type::tuple<int, bool, std::string> >();
return 0;
}
See QUICKSTART-CPP.md
for more details.
msgpack-c requires boost library. C++ version of msgpack-c itself is a header-only library and depends only on boost headers. Tests depend on boost unit test framework and are linked with it, so if you want to build them, you need to have this dependency installed.
Experimental support for removing boost dependency
For cmake:
cmake -DMSGPACK_USE_BOOST=OFF ..
NOTE: -DMSGPACK_BUILD_TESTS=ON
doesn't work with -DMSGPACK_USE_BOOST=OFF
.
For C++ compiler
clang++ -DMSGPACK_NO_BOOST your_code.cpp
-
If you build your project with cmake, you can find msgpack-c with a canonical cmake-way:
# ... find_package(msgpack REQUIRED) # ... target_link_libraries(your_target_name <PRIVATE/PUBLIC/INTERFACE> msgpack-cxx) # ...
This will search for
msgpack
cmake package in a system prefix and in prefixes fromCMAKE_PREFIX_PATH
. Note that msgpack-c depends on boost headers, andmsgpack
cmake package depends onBoost
cmake package. The library is header-only andtarget_link_libraries
command just adds path to msgpack-c headers to your compiler's include path.A usage example can be found at test-install directory.
-
If you do not use cmake, you can just add path yo msgpack-c and boost headers to your include path:
g++ -I msgpack-c/include -I path_to_boost your_source_file.cpp
You will need:
gcc >= 4.1.0
cmake >= 3.1.0
C++03:
git clone https://github.com/msgpack/msgpack-c.git
cd msgpack-c
git checkout cpp_master
cmake .
sudo cmake --build . --target install
If you want to build tests with different C++ version, you can use
MSGPACK_CXX11
, MSGPACK_CXX14
, MSGPACK_CXX17
, MSGPACK_CXX20
options.
Just replace the line
cmake .
with a line like that:
cmake -DMSGPACK_CXX20=ON .
Note that these flags do not affect installation. They just switch test cases. All files are installed in every settings.
If you don't have superuser permissions or don't want to install the library
to a system-wide prefix, you can use CMAKE_INSTALL_PREFIX
option like that:
cmake -DCMAKE_INSTALL_PREFIX=/your/custom/prefix .
Other useful options:
MSGPACK_BUILD_TESTS
(defaultOFF
): build testsMSGPACK_BUILD_EXAMPLES
(defaultOFF
): build examplesMSGPACK_32BIT
(defaultOFF
): 32bit compileMSGPACK_USE_X3_PARSE
(defaultOFF
): use Boost X3 parse (note that it requires C++14 or newer)MSGPACK_CHAR_SIGN
(not set explicitly by default): char sign to use (signed or unsigned)MSGPACK_USE_STATIC_BOOST
(defaultOFF
): statically link with boost libraries
Clone msgpack-c git repository with the command:
git clone https://github.com/msgpack/msgpack-c.git
or using GUI git client (e.g. tortoise git).
-
Checkout to
cpp_master
branch -
Launch cmake GUI client.
-
Set 'Where is the source code:' text box and 'Where to build the binaries:' text box.
-
Click 'Configure' button.
-
Choose your Visual Studio version.
-
Click 'Generate' button.
-
Open the created msgpack.sln on Visual Studio.
-
Build all.
You can get additional information including the tutorial on the wiki.
msgpack-c
is developed on GitHub at msgpack/msgpack-c.
To report an issue or send a pull request, use the
issue tracker.
Here's the list of great contributors.
msgpack-c
is licensed under the Boost Software License, Version 1.0. See
the LICENSE_1_0.txt
file for details.