Currently, tools are run off their build directory. Only "sdcc" has an install tree with a proper "make install".
This makes unpractical to remove temporary build artifacts while keeping working binaries.
It would be good to be able to install all necessary pieces in a location outside of the source tree (even with an in-source build). (at least as an option) "make install" all tools in a common prefix.
It would be good to (at least as an option) "make install" all tools in a common prefix.
That way, only one addition to PATH would allow to use all tools.
This would also help make a clean and simple integration into a Docker image.
Currently, tools are run off their build directory. Only "sdcc" has an install tree with a proper "make install".
This makes unpractical to remove temporary build artifacts while keeping working binaries.
It would be good to be able to install all necessary pieces in a location outside of the source tree (even with an in-source build). (at least as an option) "make install" all tools in a common prefix.
It would be good to (at least as an option) "make install" all tools in a common prefix. That way, only one addition to PATH would allow to use all tools.
This would also help make a clean and simple integration into a Docker image.