6 | | |
| 8 | |
| 9 | == General == |
| 10 | |
| 11 | == ChimeraX == |
| 12 | === Build System === |
| 13 | 1) Supporting IDEs |
| 14 | - may only need editable installs (will require workaround as namespace packages cannot be installed in this mode automatically) |
| 15 | - editable installs should also let us call ChimeraX with Python for rapid iteration and the C launcher for detailed crash info |
| 16 | - Zach mentioned PyCharm, LSP (Language Server Protocol), XCode |
| 17 | - Greg mentioned Visual Studio |
| 18 | |
| 19 | 2) API for getting C headers: get_include (see: numpy.get_include) |
| 20 | - {{{native-packaging}}} moves bundle header files to {{{bundle/src/include/module}}} |
| 21 | |
| 22 | 3) API for getting library directories: get_libdir |
| 23 | |
| 24 | === Infrastructure === |
| 25 | 1) Beta releases on Toolshed |
| 26 | |
| 27 | 2) Decoupling core bundle version number from the ChimeraX release number |
| 28 | |
| 29 | 3) Prereq audit after 27 June |
| 30 | |
| 31 | 4) arm64 port |
| 32 | - Tom suggests zipping x86_64 ChimeraX and arm64 ChimeraX together |
| 33 | - How best to backport M1 support from native-packaging to 1.4 release branch |
| 34 | |
| 35 | == Chimera == |
| 36 | 1) Back up the build machine to a solid state drive |
| 37 | |
| 38 | -------------------------- |