# Windows/Docker build errors with cmb-superbuild:master

**URL:** https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361
**Category:** Build & Install
**Created:** [December 11, 2019, 5:52pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361 "2019-12-11T17:52:04Z")
**Posts on this page:** 5
**Page:** 3

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [January 9, 2020, 6:37pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361/41 "2020-01-09T18:37:45Z")

</div>

@johnt That sounds like a difference in the initialization of static variables used to ensure that classes are registered. @aron.helser I don’t see immediately where pqSMTKResourceBrowser is registered with the smtk view manager. Can you point me to it?

---

<div class="post-metadata">

### Author: ![aron.helser](https://discourse.kitware.com/user_avatar/discourse.kitware.com/aron.helser/32/149_2.png) [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [January 9, 2020, 6:59pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361/42 "2020-01-09T18:59:45Z")

</div>

In pqSMTKAppComponentsAutoStart.cxx:127

```
qtSMTKUtilities::registerViewConstructor(
    "pqSMTKResourceBrowser", pqSMTKResourceBrowser::createViewWidget);
```

---

<div class="post-metadata">

### Author: ![johnt](https://discourse.kitware.com/user_avatar/discourse.kitware.com/johnt/32/147_2.png) [@johnt](https://discourse.kitware.com/u/johnt)
#### Post date: [January 9, 2020, 11:49pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361/43 "2020-01-09T23:49:28Z")

</div>

I will include @ben.boeckel since he has been drafted into the effort. There is an interesting observation to report:

I just finished a linux/debug build of cmb-superbuild:master from scratch, and

- The modelbuilder in the build tree works OK.
- The modelbuilder in the install tree works OK.
- But the modelbuilder in the package tree has the mystery “missing icons” problem.

Could the fixup-bundle script be hosing something?

---

<div class="post-metadata">

### Author: ![johnt](https://discourse.kitware.com/user_avatar/discourse.kitware.com/johnt/32/147_2.png) [@johnt](https://discourse.kitware.com/u/johnt)
#### Post date: [January 10, 2020, 10:08pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361/44 "2020-01-10T22:08:52Z")

</div>

I guess I should update our status from “yet another week goes by without a windows build” to “yet another week goes by without any modelbuilder packages…”

---

<div class="post-metadata">

### Author: ![johnt](https://discourse.kitware.com/user_avatar/discourse.kitware.com/johnt/32/147_2.png) [@johnt](https://discourse.kitware.com/u/johnt)
#### Post date: [January 13, 2020, 10:43pm UTC](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361/45 "2020-01-13T22:43:23Z")

</div>

After a few more hours working through the code, Ben figured out that the actual problem was that the smtkViewPlugin is not being included when the package gets bundled. So a one-line change to the superbuild will fix it for now. Going forward, we need to update the superbuild to find plugins automatically instead of relying on a white list.

[Previous page](https://discourse.kitware.com/t/windows-docker-build-errors-with-cmb-superbuild-master/361.md?page=2)