I will take a look and try to figure out why the dependencies are not correct for the examples. Regards, -Mike

Hi Mike, Can you change the build so that if the bridge library changes the examples will get relinked? William

This patch adds a new middleware type "tick42blp" to the current set of middleware names enumerated in middleware.c This has no impact other than to allow the tick42 blp middleware bridge to load and

Thanks Slavo. That indeed helped me resolve the issue.

Mark, see my previous post in here http://lists.openmama.org/pipermail/openmama-users/2012-July/000036.html I had the same issue. Regards, Slavo

No from within the IDE.

Mark, Are you building from a visual studio command prompt? Regards, -Mike

I’m trying to build an unmodified clone of the latest git repository in windows. I’m using VS 2010. After resolving dependencies on avis and gtest, I’m still getting errors in the build. They

Mike, I’ve finally had a chance to return to this issue. Yes, my java build appears to be succeeding. ls openmama-install/lib/libmamajni.* libmamajni.a libmamajni.la

I agree that this becomes much more cumbersome as we begin to support bridges from multiple organizations. Requiring new software just to load a new bridge that is otherwise compatible with your

I just want to throw some thoughts into the air here about simplifying the process of adding new bridges. As things stand, with OM 2.1.1.2, if I want to run a new middleware bridge I have to add

Hi Mark, Thanks for the response. My programs are actually the mamdapublisher and mamdalistener from the examples. I found I had to make some small changes to get these working. So I use the

Russell, Take a look at mamda/c_cpp/src/examples/mamdapublisher.cpp (specifically MamdaPublisher::addMamaHeaderFields). I think your issue is that you need to add more header fields, afaik at a

Hi, I wonder if anyone has come across this MAMDA publisher/listener behaviour ? I wrote a simple test MAMDA listener and publisher. In the listener I create a simple MamdaSubscription, using

Jenkins is a good choice as a CI server. Ideally, we'd want to run a small build farm targeting the main CPU / OS combos (Windows, Linux, 32-bit & 64-bit x86), but that can be for the future. Some

Mike Ritchie from J.P. Morgan was kind enough to draft this very thorough proposal and roadmap to establish continuous integration (CI) for OpenMAMA. The proposal addresses many of the challenges

From: Mike Schonberg <mschonberg@...> Normally, with refreshes enabled, mamaTransport delegates maintaining a list of subscriptions to the refresh sub-transport; however, when refreshes are

I found the problem. We previously had unnecessary #ifdef's that allowed us to conditionally compile MAMA without any refresh logic. When we removed the conditional compilation, we erroneously deleted

Thanks Mike. I will investigate further and report back when I have a second to revert to this clean state. Cheers, Mark

Thanks Mike. Would you like me to post the fix as a proper patch then? Or would you like to look through the submissions and back track on when this was introduced? Cheers, Mark