Seeking feedback before going further.
The goal is to have a build without RPC support just by passing --disable-rpc. An alternative would be --disable-http if we want to also disable REST and RPC in one shot.
Follow ups would be:
--disable-rest.--without-libevent configure option that would allow auto value for --disable-rpc and --disable-rest.
The motivation for doing this is faster builds? Is the speed up material if RPC/REST were disabled?
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
@michaelfolkson the motivation is to just have a node running where RPC could never be enabled. This could be interesting for mobile or maybe some other use cases.
But after discussion with @laanwj, there's no desire in making configure/builds/code more complex just for this. There is already the -noserver option.
Closing for now.