# Common superbuild impact

**URL:** <https://discourse.kitware.com/t/common-superbuild-impact/595>\
**Category:** Simulation Modeling Toolkit (SMTK)\
**Created:** [January 20, 2021, 6:47pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595 "2021-01-20T18:47:38Z")\
**Posts on this page:** 8\
**Page:** 1

<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 20, 2021, 6:47pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/1 "2021-01-20T18:47:38Z")

</div>

There seems to be interest in exploring the affect of the recent common superbuild update on modelbuilder packages. I took an action item to evaluate this as a trivial step, but either I didn’t understand the task (most likely) or it is not trivial.

1. My understanding of the task is to build our current cmb-superbuild:master using the “previous” common-superbuild (before it was bumped on Jan 7).

2. Trying it on my own, I first needed to comment out the `_superbuilder_check-up_to_date()` function that is in the common superbuild.

3. After doing that, there is one cmake error that the `sqlite` project is missing. I can try cherry picking the common-superbuild, but I am not going to pull on that thread without some concurrence this is a good use of time.

So if anyone is interested in seeing me continue this effort, please confirm whether or not this is the right plan and/or suggest how to move ahead.

---

<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 20, 2021, 9:40pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/2 "2021-01-20T21:40:10Z")

</div>

I hit the missing `sqlite` error in a customer’s build. You should be able to resolve it by adding `Sql` to the sub-package list in the `find_package(Qt5` call.

---

<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 21, 2021, 3:43pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/3 "2021-01-21T15:43:26Z")

</div>

Aron I don’t seem to have permission to access that repo. Can you clandestinely send me a patch file?

---

<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 21, 2021, 4:39pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/4 "2021-01-21T16:39:37Z")

</div>

Like this:

```auto
- find_package(Qt5 REQUIRED COMPONENTS Core Gui Svg Widgets)
+ find_package(Qt5 REQUIRED COMPONENTS Core Gui Svg Sql Widgets)

```

---

<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 21, 2021, 6:28pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/5 "2021-01-21T18:28:43Z")

</div>

Thanks, but this is something different, Aron, In my case, cmake is looking for sqlite as a _superbuild project_.

---

<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 21, 2021, 6:38pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/6 "2021-01-21T18:38:54Z")

</div>

OK, that’s weird. I discovered that vtk has a name-mangled copy of sqlite in its third-party dependencies,

and that QT5 wants sqlite, but will use an internal copy if one is not available, I believe. I did not see a use of sqlite in the superbuild.

---

<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 22, 2021, 3:37pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/7 "2021-01-22T15:37:43Z")

</div>

I bet it’s a linux thing, because we build python there. And perhaps there was some change in building py3.8 vs 3.7?

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.kitware.com/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.kitware.com/u/ben.boeckel)\
**Post date:** [February 21, 2021, 1:29pm UTC](https://discourse.kitware.com/t/common-superbuild-impact/595/8 "2021-02-21T13:29:26Z")

</div>

The common-superbuild has a “menu” of projects that it knows how to build. Each superbuild itself picks from this “menu” and brings its own recipes too (this is the `projects/` directory). This selection is made in `superbuild_find_projects` at the top-level. The `projects` variable contains a list of projects that are “known” in the superbuild. So the fix is to add `sqlite` to this list (because it is a known “menu item”, that’s all that’s needed).