On Thu, 2016-11-17 at 15:27 +0100, Tor Rune Skoglund wrote: > Hi List, > > it seems that one always needs to build and install the full qpidd > package including the broker when one just wants the libs and tools > to > send and receive messages. > > In some of our use cases, the broker and its queues might run on a > different server. Then, we just need the core libs and core send/rcv > tools that talk to the remote broker directly. It would be very > convenient if it was possible to avoid compiling and installing the > broker itself and all other stuff that is needed just the broker. > > We mostly build on and for somewhat "embedded" machines with limited > disk and ram, and use Gentoo. So we would like to keep the "firmware" > as > small, neat and clean as possible, and also save compile time... > > Is this possible in some simple way, e.g. using some compile flags? > Any other comments?
There isn't any straightforward way to do this from the upstream sources. The way package builders handle this is to build/install everything and then selectively take the bits required by smaller packages. For example the Fedora and RHEL packages are split up exactly as you suggest: qpid-cpp-client, qpid-cpp-server, qpid-tools, qpid-python- client etc. You could do what you want by calling the right subset of the targets that are already there (maybe adding a few more) but I don't know of anyone who has worked that out. > BR, > Tor Rune Skoglund, FourC AS > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
