windows下rabbitmq-c编译(带openssl、无需MinGW)
因为项目原因,需要使用到rabbitmq的c客户端库。首先,参见上一篇windows下openssl编译,如果已经使用cmake编译过了,则先delete cache(File-Delete Cache),否则原来的cmake缓存都在了,将仍然会出现原来的错误。
依次点击configire、generate,可以生成vs sln。如下:
最后使用VS即可生成rabbitmq.4.dll,如下:
测试自带的例子:
D:\RabbitMQ Server\rabbitmq_server-3.6.5\sbin>cd /d D:\rabbitmq-c-0.8.0-build\examples\Debug D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_listen localhost 5672 amq.direct test
Delivery 1, exchange amq.direct routingkey test
Content-type: text/plain
----
00000000: 68 65 6C 6C 6F 20 77 6F : 72 6C 64 hello world
0000000B:
Delivery 2, exchange amq.direct routingkey test
Content-type: text/plain
----
00000000: 68 65 6C 6C 6F 20 77 6F : 72 6C 64 hello world
0000000B:
Delivery 3, exchange amq.direct routingkey test
Content-type: text/plain
----
00000000: 68 65 6C 6C 6F 20 77 6F : 72 6C 64 hello world
0000000B:
Delivery 4, exchange amq.direct routingkey test
新开一个窗口,执行如下:
D:\RabbitMQ Server\rabbitmq_server-3.6.5\sbin>cd /d D:\rabbitmq-c-0.8.0-build\examples\Debug D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world" D:\rabbitmq-c-0.8.0-build\examples\Debug>amqp_sendstring localhost 5672 amq.direct test "hello world"
需要注意的是,librabbitmq的channel不是线程安全的,因此需要应用自行保证线程安全性,如下所述:
Threading
You cannot share a socket, an amqp_connection_state_t
, or a channel between threads using librabbitmq
. The librabbitmq
library is built with event-driven, single-threaded applications in mind, and does not yet cater to any of the requirements of pthread
ed applications.
Your applications instead should open an AMQP connection (and an associated socket, of course) per thread. If your program needs to access an AMQP connection or any of its channels from more than one thread, it is entirely responsible for designing and implementing an appropriate locking scheme. It will generally be much simpler to have a connection exclusive to each thread that needs AMQP service.
官方主页https://github.com/alanxz/rabbitmq-c
doc api http://alanxz.github.io/rabbitmq-c/docs/0.8.0/classes.html
剩下的就是慢慢啃主要的api了。
最新文章
- c++单例模式为什么不在析构函数中释放静态的单例对象(转)
- UnitOfWork以及其在ABP中的应用
- 如何用Endnote导入你要用的格式
- QTP11.00安装+破解详细教程
- 图像处理控件ImageGear for .NET教程如何为应用程序 添加DICOM功能(2)
- Android-简单的sdcard文件浏览
- VMware 进入bios
- [转]fedora启动telnet服务
- Ajax:Cross-Origin Resource Sharing(转)
- .net 链接oracle
- 数据库sqlite的使用
- 微信公众平台应用开发框架sophia设计不足(1)
- 设计模式六大原则-OCP
- linux视频学习4(crontab和进程)
- MDK下调试时提示AXF文件无法导入的解决方法(转)
- The Lisp Curse /Lisp魔咒
- EventBus详解
- Android为TV端助力:adb查找包名位置
- 网络IP地址
- js 中导出excel 较长数字串会变成科学计数法