Poll: How do you (re)generate s4ext file for Slicer ExtensionsIndex?

Development
1
  • I make my own s4ext file (write from scratch, copy from somewhere and modify it, etc)
  • I use the s4ext file that was generated as part of the extension build process, and re-generate it that way if I need to update s4ext
  • If I need to update something in s4ext that is already in ExtensionsIndex, I just edit it manually
  • I use ExtensionWizard to make my extensions, and I use s4ext it creates
  • I use some other approach

0 voters

Show results
2

If I need to update something in s4ext that is already in ExtensionsIndex, I just edit it manually

I sometime manually edit to only change the git hash.

3

So you should also check the manual edit option too :wink:

Jokes aside, I hope this is useful, and should also raise awareness of the developers about what is the proper procedure and that they should remember to update the CMakeLists.txt of their extension.

4

So as I :slight_smile: BUt I edit s4ext’s exactly once: when I change the fixed git hash / svn rev to HEAD. Otherwise generate from CMakeLists

1 Like