[BRLTTY] Compiling a statically linked binary

[S. Massy]

On Fri, Oct 31, 2014 at 01:18:52PM -0400, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2014/10/31 at 13:04 -0400]
> 
> >I think it is probably time to give up on the idea of a statically 
> >linked binary.  So many things are split into separate files for good 
> >reasons: drivers, config files, braille tables, key bindings, help 
> >screens, etc.  So the idea of an autonomous single binary doesn't work 
> >well anymore.
> 
> Yes, although the idea of the executable itself being statically linked is, I 
> think, still valid as it makes the executable independent from whatever shared 
> libraries may or may not be on the target system.
I agree with both of you. I've just gone through the process of creating
a statically linked version of BRLTTY and, though I did get it working
eventually, there are still many corner cases where the programme can't
find resources it takes for granted, leading to harmless errors or
missing features. There is also the fact that having just one driver
built-in isn't very flexible or practical. 

On the other hand, the ability to have a working BRLTTY install that one
can use on any system is just too useful to relinquish; as I said in a
previous e-mail, it's come in handy too many times for me to do without.

> 
> >It might be better to create a script to make it easy to install BRLTTY 
> >on any medium instead.
> 
> Yes. Amongst other things, it should also configure with 
> --enable-relocatable-install so that the whole hierarchy is self-contained.
It should probably also minimise external dependencies in general.

Cheers,
S.M.
-- 
Sebastien Massy
Montreal, Canada
Website: http://www.wolfdream.ca
Twitter: http://www.twitter.com/SMassy1
LinkedIn: http://ca.linkedin.com/pub/sebastien-massy/47/5a5/81a
Google+: https://plus.google.com/113474861330993124986/posts