TESTING.html 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. <!--#include file="header.html" -->
  2. <h2>Testing Buildroot for an Architecture</h2>
  3. <p>
  4. <h4>scripts/mkpkg script</h4>
  5. If you want to test the build of a single package you can use the mkpkg script.
  6. </p>
  7. <p>
  8. <li>$ scripts/mkpkg PACKAGE</li>
  9. </p>
  10. <p>
  11. Will make the board, and save the result in a log file.
  12. The log file resides in
  13. <li>$ log/OK/PACKAGE.log.OK</li>
  14. </p>
  15. <p>
  16. if the build succeeds and in
  17. <li>$ log/OK/PACKAGE.log.FAIL</li>
  18. </p>
  19. <p>
  20. if it cannot complete.
  21. </p>
  22. <p>
  23. By creating an alias
  24. <li>alias mk=scripts/mkpkg</li>
  25. </p>
  26. <p>
  27. it is enough to type
  28. <li>$ mk PACKAGE</li>
  29. </p>
  30. <p>
  31. mkpkg will only print out the <h4>{PACKAGE}......OK</h4> or <h4>{PACKAGE}......FAIL</h4>
  32. depending on success or failure making it easy to get an overview
  33. of the status of this specific architecture.
  34. </p>
  35. <p>
  36. It is recommended to build a simple board before running the test
  37. to get some basic things done.
  38. </p>
  39. <p>
  40. <h4>scripts/buildall.sh script</h4>
  41. </p>
  42. <p>
  43. By running this script you will run scripts/mkpkg on
  44. a lot of the packages available in Buildroot.
  45. </p>
  46. <p>
  47. You need to run the script while in the TOP directory.
  48. I.E: Where you typically run make.
  49. </p>
  50. <p>
  51. There are a few lacking, for no very good reason,
  52. but these can be easily added.
  53. </p>
  54. <p>
  55. Note that some packages will not build properly
  56. if you do not enable them using makeconfig.
  57. </p>
  58. <p>
  59. Examples are:
  60. <li>freetype</li>
  61. <li>socat</li>
  62. </p>
  63. <!--#include file="footer.html" -->