#31 Automake/libtool conversion
I've begun work to migrate mbsebbs compilation to automake; this, in turn, should ease work for making path and permissions handling more modern/flexible: I'd really prefer an installation that doesn't have the UID the daemon runs as, owning the files as they sit on the disk.
I'm opening this ticket as a place to track and coordinate my efforts. At this point, I've got my working tree compiling and installing the binaries using the non-recursive approach, the same as before except that libraries can be shared or static as ./configure and platform abilities dictate, and libmbse/libdbase are merged (neither can link without the other anyway.)
I'm about to move on to non-compiled components and it seems like this would be a good time for an initial once-over review-ish step.
I'm requesting git write access to a new "automake" branch.
There are some sub components in other areas that use libdbase and not libmbse. It may be a good idea to enable Link-Time Optimization during building to reduce the size of binaries if such libraries were merged, internally. I do agree that a more flexible build would be reasonable and far more deployable. Ultimately, this falls under Andrew's jurisdiction so I'll leave it to him.
Kevin,
I've added you to the project as a developer; that should allow you to create a branch to work on your changes. When you're finished, we will evaluate and see about merging your changes into the master branch.
On 20/12/2020 03:24, Kevin Cody wrote:
I've begun work to migrate mbsebbs compilation to automake; this, in
turn, should ease work for making path and permissions handling more
modern/flexible: I'd really prefer an installation that doesn't have the
UID the daemon runs as, owning the files as they sit on the disk.
I'm opening this ticket as a place to track and coordinate my efforts.
At this point, I've got my working tree compiling and installing the
binaries using the non-recursive approach, the same as before except
that libraries can be shared or static as ./configure and platform
abilities dictate, and libmbse/libdbase are merged (neither can link
without the other anyway.)
I'm about to move on to non-compiled components and it seems like this
would be a good time for an initial once-over review-ish step.
Don't forget modification to the install script/s such as SETUP.sh
This does not reflect any change in the install directory such as caused
by using ./configure --prefix=/home/mbse