bash script using dialog

I have created a script that I use when installing on new machines
that automatically copy over settings files from CD to their correct
place. This is done using dialog. I now want the script to show the
output of a compilation. I have tried:

dialog --backtitle "Compiling klips program" --tailbox $OUTPUT 15 45
cd /tmp/openswan* ; make programs >> $OUTPUT

where $OUTPUT is a previously created file.

The dialog does show with the box to show the text but nothing is
displayed. This is presumably because it waits for the user to exit
before actually starting the compilling in the second command. I then
tried with --tailboxbg thinking that this will background the process
and start the compilation, then showing the text in the box but all I
get is the blue background of dialog and no text box at all.

Does anyone know if I am going about this in the correct way or if
there is any other way to show the output of the compiling using
dialog. All the rest of the script is done in dialog so I dont really
want to drop the user back to the terminal to do the compiling.

Many thanks for any help

Tom

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: bash script using dialog
    ... > that automatically copy over settings files from CD to their correct ... dialog and the rest of the script. ... the script (and hence the dialog command) to continue. ... > and start the compilation, then showing the text in the box but all I ...
    (Ubuntu)
  • Re: bash script using dialog
    ... >> that automatically copy over settings files from CD to their correct ... I now want the script to show the ... start the compilation but carry on when it is finished whithout the ... through showing the compiler output or not - they dont need to see the ...
    (Ubuntu)
  • Re: [PHP] How does the Zend engine behave?
    ... all include files compiled when the script is first compiled, which would mean a cascade through all statically linked include files. ... I.e Are statically included files automatically loaded into memory at the start of a request? ... I assume the eaten memory is for something to do with compilation or caching in the ZE. ... Now suppose a second request arrives for the same script, from a different requester, am I right in assuming that the uncompiled form is loaded? ...
    (php.general)
  • Re: [PHP] How does the Zend engine behave?
    ... all include files compiled when the script is first compiled, which would mean a cascade through all statically linked include files. ... I.e Are statically included files automatically loaded into memory at the start of a request? ... I assume the eaten memory is for something to do with compilation or caching in the ZE. ... Now suppose a second request arrives for the same script, from a different requester, am I right in assuming that the uncompiled form is loaded? ...
    (php.general)
  • Re: [PHP] How does the Zend engine behave?
    ... into memory at the start of a request? ... Or when the script is initially loaded? ... assume the eaten memory is for something to do with compilation or ... Now suppose a second request ...
    (php.general)