Difference between revisions of "Talk:Compiling and getting started"
Jump to navigation
Jump to search
Tigerbeard (talk | contribs) (answer) |
|||
| Line 6: | Line 6: | ||
:The proper way is to use "make clean". --[[User:VZ|VZ]] ([[User talk:VZ|talk]]) 05:22, 22 September 2018 (MDT) | :The proper way is to use "make clean". --[[User:VZ|VZ]] ([[User talk:VZ|talk]]) 05:22, 22 September 2018 (MDT) | ||
:: Then I have a very strange Linux, because its doing something else: after "make clean" my lib files are gone, too (just tried it out). That is not what is intended. rm -rf *.o only removes the unused object files and leaved the binaries in place . --[[User|Tigerbeard]] | :: Then I have a very strange Linux, because its doing something else: after "make clean" my lib files are gone, too (just tried it out). That is not what is intended. rm -rf *.o only removes the unused object files and leaved the binaries in place . --[[User|Tigerbeard]] | ||
| + | :::OK, sorry, should have been more clear. "make clean" is supposed to clean everything, so you should do it after "make install" for example. --[[User:VZ|VZ]] ([[User talk:VZ|talk]]) 06:23, 22 September 2018 (MDT) | ||
Revision as of 06:23, 22 September 2018
g++ `wx-config --cppflags` widgetTest.cpp `wx-config --libs`
cleanup after make
After installation to a local path (configure option --prefix) the directory is filled with *.o files (maybe its the same after running make install). I think it would be useful to add the proper way to clean up those files. I delete them with rm, but I guess there is a better way... --Tigerbeard
- The proper way is to use "make clean". --VZ (talk) 05:22, 22 September 2018 (MDT)
- Then I have a very strange Linux, because its doing something else: after "make clean" my lib files are gone, too (just tried it out). That is not what is intended. rm -rf *.o only removes the unused object files and leaved the binaries in place . --Tigerbeard