Could I safely remove the build subdirectory after having compiled a program from sources?
up vote
0
down vote
favorite
Description:
When I compile a software from sources, I usually do it in the /opt
folder (don't ask my why, I don't know) by running these commands;
$ git clone < git url of the software >
$ mkdir build; cd build
$ cmake-gui ..
=> click on "configure" withincmake-gui
=> configure some paths or options (this may take some time and be tricky until I debugged all dependencies...)
=> click on "generate" withincmake-gui
, then when everything worked fine;
$ make -j4
$ sudo checkinstall
Questions:
I really like to keep the cloned sources if I later want to pull the new commits, but I wonder if I can safely remove the build/
sub-directory (which is using a lot of disk space sometimes)? Why?
And if yes, how could I keep a trace of all the options I tweaked within cmake-gui
?
Related question (why to use checkinstall
instead of make install
):
Removing sources after building from them
software-installation compiling software-sources
add a comment |
up vote
0
down vote
favorite
Description:
When I compile a software from sources, I usually do it in the /opt
folder (don't ask my why, I don't know) by running these commands;
$ git clone < git url of the software >
$ mkdir build; cd build
$ cmake-gui ..
=> click on "configure" withincmake-gui
=> configure some paths or options (this may take some time and be tricky until I debugged all dependencies...)
=> click on "generate" withincmake-gui
, then when everything worked fine;
$ make -j4
$ sudo checkinstall
Questions:
I really like to keep the cloned sources if I later want to pull the new commits, but I wonder if I can safely remove the build/
sub-directory (which is using a lot of disk space sometimes)? Why?
And if yes, how could I keep a trace of all the options I tweaked within cmake-gui
?
Related question (why to use checkinstall
instead of make install
):
Removing sources after building from them
software-installation compiling software-sources
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Description:
When I compile a software from sources, I usually do it in the /opt
folder (don't ask my why, I don't know) by running these commands;
$ git clone < git url of the software >
$ mkdir build; cd build
$ cmake-gui ..
=> click on "configure" withincmake-gui
=> configure some paths or options (this may take some time and be tricky until I debugged all dependencies...)
=> click on "generate" withincmake-gui
, then when everything worked fine;
$ make -j4
$ sudo checkinstall
Questions:
I really like to keep the cloned sources if I later want to pull the new commits, but I wonder if I can safely remove the build/
sub-directory (which is using a lot of disk space sometimes)? Why?
And if yes, how could I keep a trace of all the options I tweaked within cmake-gui
?
Related question (why to use checkinstall
instead of make install
):
Removing sources after building from them
software-installation compiling software-sources
Description:
When I compile a software from sources, I usually do it in the /opt
folder (don't ask my why, I don't know) by running these commands;
$ git clone < git url of the software >
$ mkdir build; cd build
$ cmake-gui ..
=> click on "configure" withincmake-gui
=> configure some paths or options (this may take some time and be tricky until I debugged all dependencies...)
=> click on "generate" withincmake-gui
, then when everything worked fine;
$ make -j4
$ sudo checkinstall
Questions:
I really like to keep the cloned sources if I later want to pull the new commits, but I wonder if I can safely remove the build/
sub-directory (which is using a lot of disk space sometimes)? Why?
And if yes, how could I keep a trace of all the options I tweaked within cmake-gui
?
Related question (why to use checkinstall
instead of make install
):
Removing sources after building from them
software-installation compiling software-sources
software-installation compiling software-sources
asked Nov 26 at 14:32
s.k
146110
146110
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096189%2fcould-i-safely-remove-the-build-subdirectory-after-having-compiled-a-program-fro%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown