Minor issue I ran into with the https://github.com/deech/fltkhs/tree/TheGreatConsolidation branch; on rebooting, my previously working build had a whole bunch of linker errors. Realized that the fltk and binding libraries stored in /tmp/fltkhs-0.8.0.3-third-party-build were gone, because on my Manjaro system at least, /tmp is in memory via tmpfs. I couldn't figure out a way to unregister the fltkhs package from the snapshot folder or get it to rebuild, so I had to delete the snapshot and rebuild the dependency tree. For now I have copied the output folder elsewhere so I can just restore it when necessary, but it seems like /tmp is not an ideal location for it.
(edit) A similar issue seems to happen when I build via Stack's docker mode. In this case it works fine the first time I build fltkhs and my app in one go, but then if I make any change and rebuild it fails. I'm actually not sure where it's storing the fltkhs-0.8.0.3-third-party-build folder in that case (it's not in the host system's /tmp), I guess maybe it's in the Docker image that gets thrown out but only after the executable finishes building?
Minor issue I ran into with the https://github.com/deech/fltkhs/tree/TheGreatConsolidation branch; on rebooting, my previously working build had a whole bunch of linker errors. Realized that the fltk and binding libraries stored in
/tmp/fltkhs-0.8.0.3-third-party-buildwere gone, because on my Manjaro system at least,/tmpis in memory viatmpfs. I couldn't figure out a way to unregister the fltkhs package from the snapshot folder or get it to rebuild, so I had to delete the snapshot and rebuild the dependency tree. For now I have copied the output folder elsewhere so I can just restore it when necessary, but it seems like/tmpis not an ideal location for it.(edit) A similar issue seems to happen when I build via Stack's docker mode. In this case it works fine the first time I build
fltkhsand my app in one go, but then if I make any change and rebuild it fails. I'm actually not sure where it's storing thefltkhs-0.8.0.3-third-party-buildfolder in that case (it's not in the host system's/tmp), I guess maybe it's in the Docker image that gets thrown out but only after the executable finishes building?