Changes between Initial Version and Version 4 of Ticket #20531
- Timestamp:
- Jul 2, 2026, 5:27:54 PM (13 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #20531
- Property Cc added
- Property Component Unassigned → Build System
- Property Owner set to
- Property Platform → all
- Property Project → ChimeraX
- Property Reporter changed from to
- Property Status new → assigned
- Property Summary ChimeraX bug report submission → Singularity definition
-
Ticket #20531 – Description
initial v4 3 3 Platform: Linux-6.8.0-124-generic-x86_64-with-glibc2.35 4 4 ChimeraX Version: 1.12 (2026-06-12 03:42:34 UTC) 5 }}} 5 6 Description 7 6 8 Spawned from my efforts to update to the latest Linux build environment for ChimeraX, and following on from an email conversation with Tom, Greg and Zach... up until now I've been relying on a little Singularity script that rebuilt the environment from scratch every time I needed an updated ChimeraX version to build against. The attached, put together with the help of Claude, instead builds a base SIF from the same definition used for ChimeraX's own build, and allows the latest chimerax release and daily versions to be regularly rolled into that. It's working fine for me as-is, but the best way to make sure the singularity .def stays in sync with ChimeraX's own is if it's maintained and distributed on your end. 7 9 8 10 Minor point: the Makefiles I use in my bundles use an environment variable $RELEASE to decide which ChimeraX executable to use (iirc that's not part of the standard Makefiles in the example bundles). The current implementation of this expects that... will attach an example Makefile in a follow-up email. 9 11 {{{ 10 12 Log: 11 13 Startup Messages