# SlicerRT build fails with new DCMTK

**URL:** <https://discourse.slicer.org/t/slicerrt-build-fails-with-new-dcmtk/40177>\
**Category:** Development\
**Tags:** build\
**Created:** [November 13, 2024, 5:16pm UTC](https://discourse.slicer.org/t/slicerrt-build-fails-with-new-dcmtk/40177 "2024-11-13T17:16:13Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [November 14, 2024, 12:45pm UTC](https://discourse.slicer.org/t/slicerrt-build-fails-with-new-dcmtk/40177/5 "2024-11-14T12:45:40Z")

</div>

Thanks @Mik. Did you also have this error before turning off Qt support?  
`LINK : fatal error LNK1181: cannot open input file 'ofstd.lib'`

The reason I posted this in the first place is that I had to rebuild all Slicers that I had compiled from scratch because of the same error that I now get when trying to build SlicerRT with the latest Plastimatch. So I assumed that this is a common issue that people are aware of.

What I built exactly with the latest SlicerRT (and got the error above) is [this branch](https://github.com/SlicerRt/plastimatch/tree/slicerrt-1.10.0-2024.10.30-5036f97b), which I just pushed after rebasing the previous branch `slicerrt-1.9.3-2022.06.15-77b40bd3` on the latest Plastimatch on gitlab (the same hash as what @Mik mentions).

Update: what is strange is that the said file (ofstd.lib) is there (S5R\DCMTK-build\lib\Release\ofstd.lib).

---

_[View the full topic](https://discourse.slicer.org/t/slicerrt-build-fails-with-new-dcmtk/40177)._