Phil,
There are a number of build options in configure. Most of them were
coded when we really were not sure what we wanted. However,
implementing them is two fold: 1. put a configure variable (as we have
a number). 2. Implement them in the Makefile.in files to make it work.
We implemented only a bare minimum and never went any farther for
several reasons: 1. Additional features were not really needed. 2.
building is fast. 3. modifying the Makefile.in files is complicated and
can easily break some of the base functionality needed.
I think building without shared libraries suffers a similar fate. In
the beginning Bacula had no shared libraries of its own, then we added
them. Then we added many more and in doing so lost the ability to go
back to static libraries, which has not been real loss.
Best regards,
Kern
On 07/18/2017 01:08 AM, Phil Stracchino wrote:
Kern,
I've spent several hours today trying to get the set of Bacula 9.0.1
components I want built on Solaris 11, and there seems to be a problem
in configure. (I was able to find a set of MySQL packages for Solaris
11.3 that included client libraries and headers, so I no longer need to
skip building the tools, though I still don't expect to use them.)
The short version is that --enable-build-dird=yes|no appears to do
nothing. Either you specify --client-only, and build only the filed; or
you don't, in which case the dird is ALWAYS built regardless of what you
tell configure to build. The configure output REPORTS it's going to do
what you intended:
asgard:root:~/bacula-9.0.1:68 # [...] --with-mysql=/usr/mysql/5.6
--enable-build-stored --enable-build-dird=no
or
asgard:root:~/bacula-9.0.1:68 # [...] --with-mysql=/usr/mysql/5.6
--enable-build-stored --disable-build-dird
outputs:
bat support: no
client-only: no
build-dird: no
build-stored: yes
Plugin support: yes
But then it goes ahead and builds dird anyway, even though it said it
wouldn't. I can disable building the storage daemon, but building the
director cannot be disabled except by using --client-only.
While I'm at it, I note that this configuration scheme provides no way
to build *only* the storage daemon. Not that I'm sure why anyone would
do that, but someone might want to.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
