Re: [BRLTTY] Compiling a statically linked binary

2014-10-31 Thread 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

Re: [BRLTTY] Compiling a statically linked binary

2014-10-31 Thread Dave Mielke
[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

Re: [BRLTTY] Compiling a statically linked binary

2014-10-31 Thread Nicolas Pitre
On Fri, 31 Oct 2014, Dave Mielke wrote: > [quoted lines by S. Massy on 2014/10/31 at 11:29 -0400] > > >It might still be appropriate to flash a warning message on the display > >and/or in the logs when no bindings are available. > > That's a good idea - thanks. > > What are your thoughts regard

Re: [BRLTTY] Compiling a statically linked binary

2014-10-31 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/31 at 11:29 -0400] >It might still be appropriate to flash a warning message on the display >and/or in the logs when no bindings are available. That's a good idea - thanks. What are your thoughts regarding adding a bunch of code to support built-in key table

Re: [BRLTTY] Compiling a statically linked binary

2014-10-31 Thread S. Massy
On Thu, Oct 30, 2014 at 11:41:48PM -0400, Dave Mielke wrote: > [quoted lines by S. Massy on 2014/10/30 at 14:37 -0400] > > >A further observation on compiling and using a statically linked binary > >of BRLTTY is that keybindings default tables no longer seem to be built > >into the driver(s). >

Re: [BRLTTY] Compiling a statically linked binary

2014-10-30 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/30 at 14:37 -0400] >A further observation on compiling and using a statically linked binary >of BRLTTY is that keybindings default tables no longer seem to be built >into the driver(s). The key tables never were built in. The bindings were only ever (for some

Re: [BRLTTY] Compiling a statically linked binary

2014-10-30 Thread S. Massy
Hello, A further observation on compiling and using a statically linked binary of BRLTTY is that keybindings default tables no longer seem to be built into the driver(s). Hence, one can't just copy the binary and run ./brltty. I've found it most expedient to copy the whole data directory and specif

Re: [BRLTTY] Compiling a statically linked binary

2014-10-24 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/24 at 08:58 -0400] >So here are the configure options I used to build a statically linked >binary of BRLTTY: >./configure --enable-standalone-programs --disable-speech-support \ > --disable-x --disable-api --with-screen-driver=lx \ > --with-

Re: [BRLTTY] Compiling a statically linked binary

2014-10-24 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/24 at 10:08 -0400] >> On Cygwin I used: >> >> ./autogen && ./configure -q --enable-standalone-programs >> --disable-java-bindings && make -s >I think you will need to exclude a lot of features, What may need disabling will be different from one platform to a

Re: [BRLTTY] Compiling a statically linked binary

2014-10-24 Thread S. Massy
On Fri, Oct 24, 2014 at 09:37:51AM -0400, Lee Maschmeyer wrote: > Hello, > > On Cygwin I used: > > ./autogen && ./configure -q --enable-standalone-programs > --disable-java-bindings && make -s I think you will need to exclude a lot of features, also note that you must build your screen and braill

Re: [BRLTTY] Compiling a statically linked binary

2014-10-24 Thread Lee Maschmeyer
Hello, On Cygwin I used: ./autogen && ./configure -q --enable-standalone-programs --disable-java-bindings && make -s Attached is the script that resulted from this command. I get a 0 return code when the --enable-standalone-programs is not in the command but when it is the error(s) are sho

Re: [BRLTTY] Compiling a statically linked binary

2014-10-24 Thread S. Massy
Hello, So here are the configure options I used to build a statically linked binary of BRLTTY: ./configure --enable-standalone-programs --disable-speech-support \ --disable-x --disable-api --with-screen-driver=lx \ --with-braille-driver=hw --with-text-table=en-nabcc \

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/23 at 23:04 -0400] >It does indeed work, though I had to explicitly disable a bunch of >features and packages. Please let us know which ones. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, O

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread S. Massy
On Thu, Oct 23, 2014 at 09:53:50PM -0400, Dave Mielke wrote: > [quoted lines by S. Massy on 2014/10/23 at 21:42 -0400] > > >This is off the 5.1 release tarball. Should I use the development tree? > > Yes, please. If there's still a problem, I'd like to see it resolved before > 5.2 > is formally

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/23 at 21:42 -0400] >This is off the 5.1 release tarball. Should I use the development tree? Yes, please. If there's still a problem, I'd like to see it resolved before 5.2 is formally released. -- Dave Mielke | 2213 Fox Crescent | The Bible is the

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread S. Massy
On Thu, Oct 23, 2014 at 09:12:44PM -0400, Dave Mielke wrote: > Is there any particular reason that you're trying to build such old brltty > source? This is off the 5.1 release tarball. Should I use the development tree? Cheers, S.M. > > -- > Dave Mielke | 2213 Fox Crescent | The Bible

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/23 at 20:53 -0400] >> >Is this still supported/tested? When I enable the >> >--enable-standalone-programs option, compilation aborts with complaints >> >that memcpy is being redefined. This is an example of why I keep nagging people to post the log so that we

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread S. Massy
On Thu, Oct 23, 2014 at 11:26:22AM -0400, Dave Mielke wrote: > [quoted lines by S. Massy on 2014/10/22 at 16:43 -0400] > > >Is this still supported/tested? When I enable the > >--enable-standalone-programs option, compilation aborts with complaints > >that memcpy is being redefined. > > Please p

Re: [BRLTTY] Compiling a statically linked binary

2014-10-23 Thread Dave Mielke
[quoted lines by S. Massy on 2014/10/22 at 16:43 -0400] >Is this still supported/tested? When I enable the >--enable-standalone-programs option, compilation aborts with complaints >that memcpy is being redefined. Please post a log of the build so that we can see the actual messages. -- Dave Mi