506173a7f4
Being a GUI application on Windows (with related flag in the executable header - see https://blogs.msdn.microsoft.com/oldnewthing/20090101-00/?p=19643/), OS would detect the subsystem before launching the application, and won't attach the parent console or redirected output handles from it to the application. Also, different hacks to reattach the GUI application to the console later are unreliable on different Windows versions, and work improperly (the output goes to the console after the launch command has already returned, which is wrong in batch files). This makes it extremily difficult to do CLI operations with LibreOffice on Windows, with error codes/warnings/messages/output missing or going to wrong consoles. Making an executable for CUI subsystem, on the other hand, makes Windows to allocate a console before starting it when the program is run by itself. This makes the console window to appear on screen unconditionally, even if it's hidden later when the program has started. This flashing is undesirable. But we use a wrapper executable on Windows, called soffice.exe, which is what actually launched by user, and which runs soffice.bin. This allows us to make soffice.bin the proper console application, and thus make it capable to behave properly in CLI scenarios, while avoid the console flashing when run from the soffice.exe (which would suppress the console creation using DETACHED_PROCESS creation flag to CreateProcessW). Also creating a new wrapper for console (soffice.com) allows to use command lines which omit explicit executable extension (no ".bin"), like this: "C:\Program Files\LibreOffice\program\soffice" --help which allows to continue using multiple available help resources unchanged, since .com extension is tried prior to .exe by Windows' cmd.exe. Change-Id: I089d0f30f860da6cfc781b4383f6598a08a4d238 Reviewed-on: https://gerrit.libreoffice.org/63572 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> |
||
|---|---|---|
| .. | ||
| inc | ||
| macros | ||
| source | ||
| AutoInstall.mk | ||
| CustomTarget_langmacros.mk | ||
| InstallModule_activex.mk | ||
| InstallModule_base.mk | ||
| InstallModule_calc.mk | ||
| InstallModule_draw.mk | ||
| InstallModule_extensions.mk | ||
| InstallModule_gnome.mk | ||
| InstallModule_graphicfilter.mk | ||
| InstallModule_impress.mk | ||
| InstallModule_kde.mk | ||
| InstallModule_math.mk | ||
| InstallModule_onlineupdate.mk | ||
| InstallModule_ooo.mk | ||
| InstallModule_python.mk | ||
| InstallModule_quickstart.mk | ||
| InstallModule_sdkoo.mk | ||
| InstallModule_ure.mk | ||
| InstallModule_windows.mk | ||
| InstallModule_winexplorerext.mk | ||
| InstallModule_writer.mk | ||
| InstallModule_xsltfilter.mk | ||
| InstallScript_sdkoo.mk | ||
| InstallScript_setup_osl.mk | ||
| Makefile | ||
| Module_scp2.mk | ||
| README | ||
SCript Particle installer This contains code that describes which pieces of the project should be packaged and installed - it is used to build among other things a setup_osl.inf or .ins file - that is used by solenv/bin/make_installer.pl to build the installation.