make-tips.txt 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. [[make-tips]]
  4. 'make' tips
  5. -----------
  6. This is a collection of tips that help you make the most of OpenADK.
  7. .Configuration searches:
  8. The +make menuconfig+ command offer a search tool.
  9. The search tool is called by pressing +/+;
  10. The result of the search shows the help message of the matching items.
  11. .Display all commands executed by make:
  12. --------------------
  13. $ make v
  14. --------------------
  15. or
  16. --------------------
  17. $ make ADK_VERBOSE=1 <target>
  18. --------------------
  19. .Display all available targets:
  20. --------------------
  21. $ make help
  22. --------------------
  23. .Cleaning:
  24. There are different cleaning targets available. If a full clean is
  25. necessary, you normally will get a message from OpenADK.
  26. To delete all build products (including build directories, target, host
  27. and pkg trees, the firmware and the toolchain for all targets):
  28. --------------------
  29. $ make cleandir
  30. --------------------
  31. If you even want to clean any downloaded source and your
  32. configuration +.config+:
  33. --------------------
  34. $ make distclean
  35. --------------------
  36. If you only want to clean the kernel build, because you added or
  37. removed some patch, just do:
  38. --------------------
  39. $ make cleankernel
  40. --------------------
  41. If you just want to clean all packages and wants to rebuild the firmware,
  42. (the toolchain is not deleted) just use:
  43. --------------------
  44. $ make clean
  45. --------------------
  46. .Resetting OpenADK for a new target:
  47. Delete the configuration and start from scratch:
  48. --------------------
  49. $ rm .config*
  50. $ make menuconfig
  51. --------------------
  52. OpenADK is designed to have multiple architectures and embedded system
  53. combinations configured and build without a need to rebuild everything
  54. from scratch. There is no limit, you just need to have enough disk space.