- question about building on Windows
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
toggle quoted messageShow quoted text
This approach makes sense to me because my goal from the beginning was to assign proper values to EVENT_HOME, PROTON_HOME and AVIS_HOME.
Here is a branch I fixed to build with VS2015, I did not try it on other platforms (and I won't):
I'm not done yet :-)
On 10 May 2016 at 16:50, Frank Quinn <fquinn.ni@...>
Honestly, the more I deal with these issues (which seem to come up in a different form every time someone tries to build on windows), the more I think this step by step thing that we do for dependencies needs a serious descope.
There are too many moving parts and I think OpenMAMA is trying to do too much: between 3rd party code, windows SDKs, VS versions, release vs debug builds and architectures. Instead I think we should list the library and header locations we expect for the dependency along with high level instructions on how to build (I.e build using solution files).
The issue you hit there is literally nothing to do with OpenMAMA - its a bug with libevent in your build stack - so rather than update our documentation to support every possible permutation, or specify one which we still need to constantly update, I think we should just keep it vague. I'd be interested to see if the community has any thoughts on this too.
Really the only things that are relevant to OpenMAMA are those directory paths.
I've fixed the error, no big deal, my intention here is to understand if a) I'm not following instructions properly or b) the instructions need to be updated.
You're the only person who can tell me if this is the case a)
If this is the case b) then I'll figure it out, fix it up and share the instructions that work.
Join Openmamaemail@example.com to automatically receive all group messages.