# Problem Building SMTK - 3/321/2020
**URL:** https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427
**Category:** Software Process
**Created:** [March 23, 2020, 12:03am UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427 "2020-03-23T00:03:40Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Bob\_Obara](https://discourse.kitware.com/u/Bob_Obara)
#### Post date: [March 23, 2020, 12:03am UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/1 "2020-03-23T00:03:41Z")
Last login: Sun Mar 22 19:57:27 on ttys002
[obara@Gallifrey SMTK] cd ../CMB [obara@Gallifrey CMB] ./bin/modelbuilder.app/Contents/MacOS/modelbuilder
( 7.139s) [paraview]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x7fbc136e4d40): No proxy that matches: group=sources and proxy=SMTKResourceImporter\_15046859196980938234 were found.
Note that this is after John’s push to in theory fix this properly - do I have to do anything special to rebuild \_ i’ve tried running cmake and ninja but I still have this error.
@dcthomp @johnt @ben.boeckel
---
### Author:  [@johnt](https://discourse.kitware.com/u/johnt)
#### Post date: [March 23, 2020, 12:13am UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/2 "2020-03-23T00:13:09Z")
I presume this occurs with _any_ .sbt or .sbi file? I cannot reproduce the error with, for example, the `viewLabelTest.sbi` file in smtk/data. I’m using linux (Ubuntu 16.04) with smtk:master and cmb:master.
Hmm, I see that I have not updated my cmb-superbuild to the current ParaView sha. I will rebuild and retest.
Update, retested, still works on linux.
---
### Author:  [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [March 23, 2020, 12:11pm UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/3 "2020-03-23T12:11:20Z")
@Bob_Obara If this is still an issue I’d be happy to help you debug.
---
### Author:  [@Bob\_Obara](https://discourse.kitware.com/u/Bob_Obara)
#### Post date: [March 23, 2020, 1:35pm UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/4 "2020-03-23T13:35:12Z")
Hey T.J.,
That would be great! - I’ve started a meeting: [https://meet.google.com/txm-rvwq-wmh](https://meet.google.com/txm-rvwq-wmh)
Talk with you soon!
Bob
Robert M. O’Bara, MEng.
Assistant Director of Scientific Computing
Kitware Inc.
1712 Route 9
Suite 3000
Clifton Park, NY 12065
Phone: (518) 881- 4931
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [March 23, 2020, 3:27pm UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/5 "2020-03-23T15:27:13Z")
As @tj.corona noted:
> The syntax for that string is dictated by Qt, not us, but there is [a bit of machinery](https://gitlab.kitware.com/cmb/smtk/-/blob/master/smtk/extension/paraview/appcomponents/plugin/pqSMTKRegisterImportersBehavior.cxx#L88) behind registering importers with paraview.
It would be nice to document this a little bit more for people writing importers. Also, there are some UX improvements we could make to modelbuilder’s File-\>Import menu item. Specifically, it lists extensions for all the registered import operations, but doesn’t have an “`Supported formats (...)`” default that combines all the extensions. That means you often end up with an empty list of files in the directory you _know_ has your data:
You have to select the file type below:
But if you use File-\>Open instead of File-\>Import, you see:
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [March 23, 2020, 4:05pm UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/6 "2020-03-23T16:05:17Z")
One of SMTK’s big customers is often adding an “all supported types” entry manually.
---
### Author:  [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [March 23, 2020, 4:10pm UTC](https://discourse.kitware.com/t/problem-building-smtk-3-321-2020/427/7 "2020-03-23T16:10:38Z")
> [@dcthomp](#):
>
> It would be nice to document this a little bit more for people writing importers.
People writing importers need only register their import operation with the importer group. More documentation is needed for operator and resource registration, but I think the success we have seen with the copy-paste-modify approach makes this less urgent than other tasks on our to-do list.
> [@dcthomp](#):
>
> Specifically, it lists extensions for all the registered import operations, but doesn’t have an “ `Supported formats (...)` ” default that combines all the extensions.
We definitely need this as an option. The class to extend is `pqImportIntoResourceReaction`. A little bit of regex-fu on `smtk/extension/paraview/appcomponents/plugin/pqSMTKImportIntoResourceBehavior.cxx:134` is all we would need. MRs welcome!