Re: Recent OpenMAMA RPM Build Failures and Scons
Although this issue is still at large, I can confirm that the latest master branch of scons has fixed the issue though, so we're basically waiting on Scons to release 3.0.2.
In the meantime I'll try and investigate some workarounds since if its not fixed before our next OpenMAMA release (which im expecting to cut shortly after the current outstanding PRs are closed), we'll have a real headache on our hands.
From: Frank Quinn
Sent: Tuesday, January 2, 2018 9:50:05 PM
Subject: Recent OpenMAMA RPM Build Failures and Scons
I have just submitted a batch of changes which introduce OpenMAMA integration headers (so that bridges and plugins can be compiled without requiring access to OpenMAMA’s code matching the library you’re linking against – more detail on that to come).
During CI, an error was spotted in RPM build on RH7 / Fedora but to put everyone’s mind at ease (or not), it looks to be unrelated to recent changes. Instead, it appears to be a bug in scons: http://scons.1086193.n5.nabble.com/more-Java-scons3-issues-td42570.html.
Hopefully it will be fixed before the next release since this is how we generate all of our cross platform RPMs. In the meantime if anyone is feeling any particular appetite to try porting OpenMAMA to cmake, please let me know. With the recent vcpkg changes now awaiting merge upstream, that will be the next devops priority. Unfortunately the cracks in scons and our supporting (python 2.x) infrastructure are starting to show as time is moving forward. We are having issues with MSVC detection in recent versions of Visual Studio 2017 too, so this may become pressing fairly soon.
T: +44 (0) 28 8678 8015