-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve installation for non-depends builds #4
Comments
@ariard can you post more details here? Main thing I'd like to know is how you installed capnp (via package manager or with manual install) and what platform or distro you used to make sure I can reproduce the problems. If you have still have the build commands you used or any error messages / build output, it'd be great to post that as well. Thanks! |
Talked to @ariard, turns out he was doing a depends build of capnproto and libmultiprocess, but a non-depends build of bitcoin itself, due to not passing The other thing that should be be done is to update the build-osx and build-unix files to mention how to install capnproto and libmultiprocess as optional dependencies, maybe just linking to instructions at the bottom of the libmultiprocess README |
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
Clarify need to specify --prefix with depends If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
If not cross compiling, it might actually be nice for it to be picked up automatically. But for now clarify the readme to try to minimize confusion. chaincodelabs/libmultiprocess#4 (comment) chaincodelabs/libmultiprocess#5 (comment)
See #96. |
bitcoin/bitcoin#16367 (review) reported various problems getting multiprocess code to build outside the
make depends
system. I've only focused onmake depends
builds so far, but would like to create libmultiprocess packages and add better instructions to make installation in other contexts easier.The text was updated successfully, but these errors were encountered: