Some changes have just been added to the origin/next branch! [noreply] COMMON: Added new method for finding a file in a PATH

Some changes have just been added to the origin/next branch! [noreply] COMMON: Added new method for finding a file in a PATH

Some changes have just been added to the origin/next branch! [Frank Quinn] Added some fixes for Visual Studio on

Some changes have just been added to the origin/next branch! [Frank Quinn] Added some fixes for Visual Studio on

Some changes have just been added to the origin/next branch! [Frank Quinn] Added some fixes for Visual Studio on

Some changes have just been added to the origin/next branch! [fquinn.ni] PLAT-839: Default value of mama.msg.allowmodify changed from "false" to mama/c_cpp/src/c/mama.c Results for

Some changes have just been added to the origin/next branch! [noreply] Fixed valgrind reported issues with unit tests

Some changes have just been added to the origin/next branch! [fquinn.ni] PLAT-839: Default value of mama.msg.allowmodify changed from "false" to mama/c_cpp/src/c/mama.c Results for OpenMAMA Next

Some changes have just been added to the origin/next branch! [fquinn.ni] PLAT-839: Default value of mama.msg.allowmodify changed from "false" to mama/c_cpp/src/c/mama.c Results for OpenMAMA Next

Some changes have just been added to the origin/next branch! [noreply] Fixed valgrind reported issues with unit tests

Some changes have just been added to the origin/next branch! [noreply] Fixed valgrind reported issues with unit tests

From: Keith Rudd Sent: 26 October 2016 15:52 To: 'Glenn McClements' <gmcclements@...> Subject: RE: Should we make the jump to cmake? A bit late on this trail, but my input is that cmake would be a

Yeah that ticket exists mainly to see if we can avoid multiple build targets – we already have a rat’s nest of build targets on windows between architecture, debug, optimized and debug so I’m

I was wondering if we need to think about multiple build targets – user dev, mama runtime, bridge dev etc. Or is that more complicated than necessary. Also, (and I may just be out of date

Yeah you’ve touched on what I said on the other thread there – the libs are actually fine as-is but the headers are definitely missing which are required for bridge development. Honestly I’ve

Yeah we have figured out the source code issues and I’ve drawn attention to it on the cmake thread – Its Monday morningJ When you have something you want me to try I’m happy to clone it and

As Reed mentioned we currently use CMake. I think the OpenMAMA devs were considering going there at one point but mysteriously lurched in the direction of Scons within days of Tick42 deciding to use

Thanks Tom, You can actually build a bridge fine without having to rebuild OpenMAMA, but you do need to point your project to the source of OpenMAMA for a few internal header files which aren’t

Hi Frank I’ve not found it possible to do bridge development (on windows anyway) without building OpenMAMAJ It may be possible though. I have just taken a path of least resistance. Let us

Some changes have just been added to the origin/next branch! [noreply] Updated dependency directory structure expected