qpid-proton.dll I built doesn't have symbols from codec.h exported, so it look s like I'm missing qpid_proton_EXPORTS define, does it make sense?

Thanks

Dmitri

Regards,

Dmitri Fedorov

Software Architect

Solace Systems, Inc.

Ottawa, ON Canada

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

On 10 May 2016 at 09:37, Frank Quinn <fquinn.ni@...> wrote:

Hi Dmitri,

I wanted to do things like that but they kept changing them so I gave up (that's why we just point to their build method now). You'll find the latest list that I use in the travis CI environment for the ZeroMQ bridge (it uses qpid payload by default):

https://github.com/fquinner/OpenMAMA-zmq/blob/master/.travis.yml

That'll be for qpid 0.10.0 though - doubtless it has changed again since then too.

Cheers,

Frank

On Tue, May 10, 2016 at 2:32 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:

Thanks Frank,

Do you think OpenMAMA Wiki should list cmake macros that disable functionality OpenMAMA doesn't need?

If you have such list, please send it my way, I can validate it.

Regards

Dmitri

Regards,

Dmitri Fedorov

Software Architect

Solace Systems, Inc.

Ottawa, ON Canada

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

On 9 May 2016 at 18:40, Frank Quinn <fquinn.ni@...> wrote:

Hi Dmitri,

Yeah that will be 32 bit. They want you to generate 64 bit solution files by running (cmake standard):

cmake -G "Visual Studio 10 Win64"

(Changing IDE version to taste)

Yeah we don't use any of the bindings just proton-c. There are a bunch of other cmake macros to disable the extra bindings.

We did a lot of work in the last release to make our solution files more usable, but as with all building on windows, its the consistency of 3rd party library naming and layout which is one of the biggest hinderences. See rant here: http://fquinner.github.io/2015/09/20/porting-openmama-zmq-to-windows/ :)

Cheers,
Frank

On Mon, 9 May 2016 23:28 Dmitri Fedorov, <dfedorov.solace@...> wrote:

Hi Frank,

I'm just done building Qpid-Proton.

BTW it (Qpid-Proton) has only WIn32 build, does it mean I'm going to have only 32 bit OpenMAMA build?

I mistakenly rebuilt swig under Windows for it - do I need this swig dependency if I don't want any language bindings in Qpid-Proton? Does OpenMAMA use Qpid-Proton language bindings?

FYI I'm building under VS2015 and while doing from scratch most of the time I spent building Qpid-Proton (and I'm still not sure I've done it properly).

Cheers

Dmitri

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

On 9 May 2016 at 14:53, Frank Quinn <f.quinn@...> wrote:

Hi Dmitri,

 

Looks like a C&P error from when this document was pulled across – see original instructions here:

 

http://wiki.openmama.org/index.php/Building_Libevent

 

Last time I built on windows though I don’t think I needed this step anymore, so maybe that was only for Visual Studio 2008 which is what I was using when I originally created those instructions.

 

Try going ahead without it and let me know how you get on so I can update documentation Instead try building with the libevent solution file in the WIN32-Prj subdirectory.

Cheers,

Frank

 

Frank Quinn, Principal Software Engineer
Tel: +44 (0) 28 9568 0209 (Ext: 3592)
24-26 Adelaide Street, Belfast, Northern Ireland, BT2 8GD
www.srtechlabs.com

SR.LABS Proven High Speed Electronic Trading Solutions

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Dmitri Fedorov
Sent: 09 May 2016 19:41
To: openmama-dev <openmama-dev@...>
Subject: [Openmama-dev] question about building on Windows

 

In Wiki page on building under Windows for libevent:

 

https://github.com/OpenMAMA/OpenMAMA/wiki/Building-on-Windows#libevent

 

There is the following sentence I have a question about, please:

 

> At this point there is an additional step which is required in order to work

> around a bug in the libevent libraries. Once the nmake command has

> completed, navigate to the ''include'' directory. Open the file ''event.h'', and

> add #include along with the other includes (yes - after compilation... don't

> ask). When complete, save the file and exit.

 

I'm puzzled by this instruction:

> add #include along with the other includes

 

Could someone explain it to me, please?

Add where? Add what, an empty #include?

What "other" includes? 

 

Thank you in advance.

 

Regards,

Dmitri Fedorov

Software Architect

Solace Systems, Inc.

Ottawa, ON Canada

 

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. SR Labs LLC

_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev