# OK to bump boost?
**URL:** https://discourse.kitware.com/t/ok-to-bump-boost/315
**Category:** Software Process
**Created:** [September 11, 2019, 7:06pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315 "2019-09-11T19:06:07Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 11, 2019, 7:06pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/1 "2019-09-11T19:06:07Z")
Hi all, I am hearing reports from some people on Windows that Boost 1.70 is needed to build with VS 2019. Does anyone have objections to moving the SMTK/CMB superbuild to boost 1.70?
---
### Author:  [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [September 11, 2019, 7:21pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/2 "2019-09-11T19:21:28Z")
+1
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 12, 2019, 11:36am UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/3 "2019-09-12T11:36:49Z")
@aron.helser Bug me today and we’ll get a MR up to modify the superbuild.
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [September 12, 2019, 12:34pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/4 "2019-09-12T12:34:38Z")
Note that MSVC 15.0 does not exist as coded here
[https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/win32/boost.cmake#L19](https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/win32/boost.cmake#L19)
see : [https://en.wikipedia.org/wiki/Microsoft\_Visual\_C%2B%2B](https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B)
I have a version of this file I use that properly constructs the msvc\_ver per the MSVC\_TOOLSET\_VERSION as FindBoost.cmake does in CMake
Also note that remus seemed to have link issue on windows with boost 1.70
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 12, 2019, 12:45pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/5 "2019-09-12T12:45:10Z")
> [@abray](#):
>
> Note that MSVC 15.0 does not exist as coded here
> [https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/win32/boost.cmake#L19](https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/win32/boost.cmake#L19)
Sounds like a great MR! 🙂
> [@abray](#):
>
> Also note that remus seemed to have link issue on windows with boost 1.70
@aron.helser and I worked through that yesterday by modifying `projects/cmb.cmake` so that remus and zeromq were not dependencies of modelbuilder. We will eventually need remus for aeva, but not quite yet — and in any event, that dependency really shouldn’t be there; we need to pull out the part of SMTK that does external meshing into a new library and make that depend on remus.
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [September 12, 2019, 1:01pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/6 "2019-09-12T13:01:52Z")
Note another oddity I found (on windows) is that the build seems to put the boost dlls in the install/lib dir at first, then eventually they also end up in the install/bin. There is no reason for the dlls to be in the lib dir on windows.
ALSO, it seems something else is building boost as I actually have 2 boost dlls for each component, for example :
- boost\_atomic-vc141-mt-gd-x64-1\_66.dll
- boost\_atomic-vc141-mt-x64-1\_66.dll
the `gd` means debug, but this is a release ninja build (using the msvc 2017 compiler)
---
### Author:  [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [September 12, 2019, 2:27pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/7 "2019-09-12T14:27:03Z")
> [@dcthomp](#):
>
> we need to pull out the part of SMTK that does external meshing into a new library and make that depend on remus
+1
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 12, 2019, 6:54pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/8 "2019-09-12T18:54:30Z")
> [@abray](#):
>
> … another oddity I found (on windows) is that the build seems to put the boost dlls in the install/lib dir at first, then eventually they also end up in the install/bin. There is no reason for the dlls to be in the lib dir on windows.
This copying is done in `superbuild/projects/win32/scripts/boost.copylibs.cmake`. Boost’s own build system is putting the files in the wrong location. The superbuild is trying to leave boost alone and just work around it.
I couldn’t find what was generating the debug build of boost, but that may be another thing Boost’s bjam system does automatically.
---
### Author:  [@chart3388](https://discourse.kitware.com/u/chart3388)
#### Post date: [September 13, 2019, 2:33pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/9 "2019-09-13T14:33:17Z")
I’m working to find to determine if we can move to VS 2019. Right now we use 2017 and passing -vcvars\_ver=14.0
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 13, 2019, 3:27pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/10 "2019-09-13T15:27:25Z")
@chart3388 Just to be clear, we are not talking about _requiring_ VS 2019, just supporting it.
---
### Author:  [@chart3388](https://discourse.kitware.com/u/chart3388)
#### Post date: [September 19, 2019, 6:58pm UTC](https://discourse.kitware.com/t/ok-to-bump-boost/315/11 "2019-09-19T18:58:14Z")
duh. My bad 🙂