For me, running with instdir/program/soffice.exe doesn't show std::cout output in the terminal. Running with instdir/program/soffice.bin does. On Mon, Jul 1, 2024 at 9:15 PM Heiko Tietze <heiko.tietze@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > In cygwin environment, don't you run instdir/program/soffice.exe? Works well here. > > > On 01.07.24 8:42 PM, Sahil Gautam wrote: > > Hi, I successfully built libreoffice on windows using LODE. The problem is that > > I cannot see stdout on the terminal, or in vscode's terminal. I rely on that for > > checking if opening this dialog trips this breakpoint or not, and how many times > > does it do so. using a debugger seems a good choice, but it's a hassle > > considering that UI can trigger a function changing colors n times, and I don't > > want to press F5 n times, it's not feasible. Is there any way to get the stdout > > on the terminal? I tried ./..soffice > log.file, but didn't get anything. If not > > then n times F5 (continue the debugger) will be the only option. I use > > `std::cout << "string here" << std::endl;` in the function calls. Regards Sahil > > Gautam