You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since rua copies all packages to the .cache dir for building, they're naturally deleted when it's done installing. This leads to updates of the same package recompiling everything from scratch, whereas merging from upstream and then compiling would get the latest version of the package and would only recompile the files that have changed.
Is there any chance that rua could try to preserve the compilation for future updates of the package? Or could it maby be a user option for all packages/per package to preserve the build dir once it's done?
The text was updated successfully, but these errors were encountered:
In general, incremental compilation results in a less-optimized binary but faster build times. Usually it's used for developers rebuilding an application alot when working on it.
A more usual way you could achieve this would be to use ccache (or sccache) to cache file build objects depending on your language (C, C++, obj-C, obj-c++ for ccache, c/c++ or rust for sccache).
Not sure about other languages.
Since rua copies all packages to the .cache dir for building, they're naturally deleted when it's done installing. This leads to updates of the same package recompiling everything from scratch, whereas merging from upstream and then compiling would get the latest version of the package and would only recompile the files that have changed.
Is there any chance that rua could try to preserve the compilation for future updates of the package? Or could it maby be a user option for all packages/per package to preserve the build dir once it's done?
The text was updated successfully, but these errors were encountered: