Closed RyuMaster closed 5 years ago
I don't think we should. But I'm happy to upload them every time something changes to some server (could even be public for everyone).
That would be nice.
Also then, is it possible to add some flag, that would ignore stub generation? Right now, I have to manually delete it from makefile, every time I git pull and build for windows
The problem with premade stubs is that I don't know how correct they actually are - since they presumably depend in theory on your exact version of jsonrpccpp
. Thus this is all a hacky solution - so I don't want to make it too official.
Why can you build jsonrpccpp
fine but not the stub generator in the first place?
I believe that stub-generation on Windows works now, so we can close this.
Also note that if we generate a source release (make dist
), then the stubs will be included in it. So this is/was mostly a problem for working from the repository directly.
Can we keep RPC generated stubs on github? On Windows, there is no easy way to generate those, i.e. library I have under msys can be only build without rpc-stubs support. So I need to switch to Linux, build there, then copy-past back on every clean update.