[rabbitmq-discuss] compiling rabbitmq-c under mingw

Fri Jul 23 20:56:21 BST 2010

Jim,
  will you be making the changes you have made available? I have been
thinking of compiling the libRabbitMQ-C library, but have not found the time
yet.

On Fri, Jul 23, 2010 at 21:46, Jim Irrer <irrer at umich.edu> wrote:

> Ok, that was no help at all,    :)
> but I got it working.
>
> The big key is to replace all of the socket calls with Windows
> compatible calls (which you probably did):
>
> write --> sendto
> read --> recvfrom
> close --> closesocket
> htons macro --> htons function
> use MS inet_addr function
> call WSAStartup before you do anything
> (not sure if I listed all of them)
>
> It seems to me that generating code on site using Python is
> a little heavy handed - requires installation of Python.  Simpler
> would be to package code for each protocol version and then
> control which was being used with #if statements.  Just a suggestion.
>
> Thanks,
>
> - Jim
>
> Jim Irrer     irrer at umich.edu       (734) 647-4409
> University of Michigan Hospital Radiation Oncology
> 519 W. William St.             Ann Arbor, MI 48103
>
>
> On Wed, Jul 14, 2010 at 6:11 PM, David Wragg <david at rabbitmq.com> wrote:
>
>> Hi Jim,
>>
>> Jim Irrer <irrer at umich.edu> writes:
>> > I know this is experimental, but I'm trying to compile the rabbitmq-c
>> libs
>> > under mingw on Windows.
>>
>> The work to support building rabbitmq-c under mingw still lives in a
>> branch.  Please checkout bug22825, and read README.windows carefully.
>>
>> David
>>
>> --
>> David Wragg
>> Staff Engineer, RabbitMQ
>> SpringSource, a division of VMware
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>

-- 
---
John Apps
(49) 171 869 1813
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100723/1d2918f7/attachment-0001.htm>