# Missing output from Windows Powershell scripts (C++ / Qt project)

**URL:** <https://travis-ci.community/t/missing-output-from-windows-powershell-scripts-c-qt-project/6340>\
**Category:** Windows\
**Created:** [December 6, 2019, 10:04pm UTC](https://travis-ci.community/t/missing-output-from-windows-powershell-scripts-c-qt-project/6340 "2019-12-06T22:04:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![trisyoungs](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@trisyoungs](https://travis-ci.community/u/trisyoungs)\
**Post date:** [December 6, 2019, 10:04pm UTC](https://travis-ci.community/t/missing-output-from-windows-powershell-scripts-c-qt-project/6340/1 "2019-12-06T22:04:26Z")

</div>

I have a modestly complex C++ project that requires Qt, Freetype, and FTGL. The Windows version is proving tricky, but after some experimentation on local Docker containers I was able to get a build script to:

- Download and install Qt silently
- Download and build Freetype 2.10.1
- Download and build FTGL (which requires Freetype)
- Finally, build my project (Dissolve)

However, getting this to work in the (admittedly early-stage) Windows VMs within Travis has proven to be incredibly problematic.

I have a sequence of Powershell scripts to tackle different parts of the build (Qt, prerequisites, Freetype build etc.) independently, but I am getting failures in the Freetype section. I seem to get output from only selected commands in the [related ps1 script](https://github.com/trisyoungs/dissolve/blob/develop/ci/windows/build.serial.gui.freetype.ps1) in the Travis logs. The last failed job can be found here: [https://travis-ci.com/trisyoungs/dissolve/jobs/264225354](https://travis-ci.com/trisyoungs/dissolve/jobs/264225354)

I feel like I’m close to a working Windows build, but must be missing something obvious, and without debug builds on Windows systems at the present time, determining the exact cause of my build issue is tricky. I have no encrypted secrets in my Travis repo setting, nor the yml file (removed these a while ago in order to debug my OSX build).

Any hints would be gratefully received at this point!

Cheers,  
Tris.

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [December 6, 2019, 10:43pm UTC](https://travis-ci.community/t/missing-output-from-windows-powershell-scripts-c-qt-project/6340/2 "2019-12-06T22:43:31Z")

</div>

Possible duplicate of

> [@Stderr output is shown after the build log rather than inline](https://travis-ci.community/t/stderr-output-is-shown-after-the-build-log-rather-than-inline/5124):
>
> Reported in [Python: os.system("git clone") does not shows any output from command](https://travis-ci.community/t/python-os-system-git-clone-does-not-shows-any-output-from-command/5117). Related: [Stderr tty appears later in log / visual studio build tools + vswhere](https://travis-ci.community/t/stderr-tty-appears-later-in-log-visual-studio-build-tools-vswhere/1594). [Test shows](https://travis-ci.org/native-api/test_travis/builds/586325976) that stdout output is correctly displayed inline, but any stderr output is displayed at the end of the log, after the “Your build exited with…” message: $ which python; python --version python -c 'if True: import subprocess subprocess.check\_call("echo bla-bla-bla", shell=True) subprocess.check\_call("echo bla-b…