Typically non-packaged library or software are install under the /opt folder.
Making it usable by different users on the system.
The dedicated install script could then simply adding the execution path as such:
export PATH=$PATH:/opt/fruitbox/rpi4 in /etc/profile
Or even better put a script like /etc/profile.d/fruitbox.sh which will detect the pi version through /proc/cpuinfo and set the proper PATH.
Or symlink the right build within /opt/fruitbox/bin and add that path to the system.
Doing so, fruitbox could be call from anywhere, like any other CLI.
Only issue at the moment, the code write and read files (fruitbox.ini, fruitbox.log) based on the CWD.
Putting it here as a simple QoL improvement.
I could give it a look myself, but been decades I've touch C++
Typically non-packaged library or software are install under the
/optfolder. Making it usable by different users on the system.The dedicated install script could then simply adding the execution path as such:
export PATH=$PATH:/opt/fruitbox/rpi4in/etc/profileOr even better put a script like/etc/profile.d/fruitbox.shwhich will detect the pi version through/proc/cpuinfoand set the proper PATH. Or symlink the right build within/opt/fruitbox/binand add that path to the system.Doing so,
fruitboxcould be call from anywhere, like any other CLI. Only issue at the moment, the code write and read files (fruitbox.ini,fruitbox.log) based on the CWD.Putting it here as a simple QoL improvement. I could give it a look myself, but been decades I've touch C++