Re: question about building on Windows
Frank Quinn <fquinn.ni@...>
toggle quoted messageShow quoted text
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.
On Tue, 10 May 2016 21:06 Dmitri Fedorov, <dfedorov.solace@...> wrote: