VCL Workbenches
TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate
VCL Workbenches
VCL Workbenches are standalone applications that use VCL library to demonstrate or test different capabilities of this library.
If you take a look into the vcl/workben
, you will see several workbenches that are actually built during the build process. These are some of them:
- commonfuzzer
- fftester
- icontest
- listfonts
- listglyphs
- minvcl
- minweld
- mtfdemo
- svdem
- svpclient
- svptest
- vcldemo
Debugging executables
LibreOffice has a number of bundled demo executables in the VCL module. To debug these, you first set the LOTRACE environment variable to point to your debugger. On Linux, this is:
$ export LOTRACE="gdb --args"
On Windows you can start the executable in Visual studio with:
$ export LOTRACE="\"path_to_your_devenv.exe\"" /debugexe"
with path_to_your_devenv.exe being the absolute path + devenv.exe. This will start Visual studio and you start the test directly from the UI.
On macOS you no longer have access to gdb which has been replaced by lldb. However you can still use LOTRACE through
$ export LOTRACE="lldb --"
To run the app, you use the bin/run script:
$ bin/run vcldemo
Alternative Debugging Method
There are alternative ways to do debugging, for example you may set URE_BOOTSTRAP
and LD_LIBRARY_PATH
and/or SEARCH_PATH
variables manually.
You can use the ./bin/run
script itself to know the values, by uncommenting the last lines of it. For example, these are the results for Linux when build is done inside /home/user/libreoffice/core/
:
$ ./bin/run minvcl Setting env variables and running workdir/LinkTarget/Executable/minvcl setting URE_BOOTSTRAP to: file:///home/user/libreoffice/core/instdir/program/fundamentalrc setting LD_LIBRARY_PATH to /home/user/libreoffice/core/instdir/program setting search path to: /home/user/libreoffice/core/instdir/program execing: /home/user/libreoffice/core/workdir/LinkTarget/Executable/minvcl