# Feedback from Windows integration for a CMake + Qt + C + Python + Perl project

**URL:** <https://travis-ci.community/t/feedback-from-windows-integration-for-a-cmake-qt-c-python-perl-project/1706>\
**Category:** Windows\
**Created:** [January 7, 2019, 4:55pm UTC](https://travis-ci.community/t/feedback-from-windows-integration-for-a-cmake-qt-c-python-perl-project/1706 "2019-01-07T16:55:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jayvdb](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/jayvdb/32/1966_2.png) [@jayvdb](https://travis-ci.community/u/jayvdb)\
**Post date:** [June 17, 2019, 8:41am UTC](https://travis-ci.community/t/feedback-from-windows-integration-for-a-cmake-qt-c-python-perl-project/1706/4 "2019-06-17T08:41:14Z")

</div>

> [@eberkund](#):
>
> +1 for refreshenv

See [RefreshEnv for bash](https://travis-ci.community/t/refreshenv-for-bash/3753) for a hack to get refreshenv working.

> [@Lekensteyn](#):
>
> msbuild is not available in PATH

I suggest you use choco package `vswhere` to locate the VS build tools available on the box.  
It has a `-legacy` mode for pre-2017 tools. [Can it be used to find earlier than VS 2017 · Issue #187 · microsoft/vswhere · GitHub](https://github.com/microsoft/vswhere/issues/187)  
It is definately on the box, as I had to remove it for my builds, in order to confirm that my project was buildable without VS compilers, so I have

```
    - rm -rf
        "/c/Program Files (x86)/MSBuild"
        /c/Windows/Microsoft.NET/Framework/v4.0.30319/msbuild.exe

```

That is probably where you will find `msbuild.exe`.

---

_[View the full topic](https://travis-ci.community/t/feedback-from-windows-integration-for-a-cmake-qt-c-python-perl-project/1706)._