cc-build

Provisional only. I'll check and tidy this later... PROMISE 

Beg/borrow/steal the latest source you can can lay your hands on; ask Franklin, scour github, the seti Discord.,.. Or, do what I did, at least to get started...

git clone https://github.com/setiastro/cosmicclarity.git
cd cosmicclarity
python3.12 -m venv venv
pip install -r requirements.txt

At this point, you'll see how hopelessly old the git really is! So...
pip install pyinstaller xisf pyqt6 opencv-python-headless sep onnxruntime scikit-image lazy-loader

 build

pyinstaller --copy-metadata xisf setiastrocosmicclarity_darkstar.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity_denoise.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity_satellite.py

the _internal folder

When the .py has been built, your binary appears at e.g. dist/SetiAstroCosmicClarity/SetiAstroCosmicClarity Copy the _internal folder to the main directory along with the SetiAstroCosmicClarity binary. After the build of each module, copy the binary to the main folder and merge the respective _internal

--- --- ---

binary names
SASPro expects the following names for the binaries:
setiastrocosmicclarity_darkstar
SetiAstroCosmicClarity
SetiAstroCosmicClarity_denoise
setiastrocosmicclarity_satellite

Rename as necessary. For example:
 cp -a setiastrocosmicclaritylinux SetiAstroCosmicClarity

build isues
 getting sep recognised
copy
sep.cpython-312-x86_64-linux-gnu.so
from cosmicclarity/venv/lib64/python3.12/site-packages
to the
_internal folder in the main directory

satellite 

From the dist/SetiAstroCosmicClarity_satellitelinux/_internal 

folder, copy these:

lazy_loader
lazy_loader-0.4.dist-info 
rawpy

rawpy-0.25.1.dist-info

rawpy.libs

scikit_image-0.25.2.dist-info

scipy

scipy-1.16.3.dist-info

scipy.libs

skimage

to the _internal folder in the main directory

the ai  onnx and  pth files
Make  a new folder  to contain the binaries and  the  ai stuff. An  easy way to do this is  to  download the  current  cc  from the  setiastro site  and simply replace  the  binaries with the  ones you built AND  of  course the  _internal along with it.
 --- --- ---

.spec file to build Thanks to the setiastro discord, we now have a .spec file which builds all the binaries. Make a venv, install the requirements.txt and the other stuff listed above and pyinstaller master.spec https://discord.com/channels/1257377319765413961/1452498766757368001

The binaries and _internal folder created under dust are then dropped into an existing folder with containing theai pth and onnx files. An easy way to do this is to download the pre built cosmic clarity_linux and overwrite the respective files therein with your build. Much more elegant than my brute force and ignorance method...