migrating.txt 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. [[migrating-from-ol-versions]]
  4. == Migrating from older Buildroot versions
  5. Some versions have introduced backward incompatibilities. This section
  6. explains those incompatibilities, and for each explains what to do to
  7. complete the migration.
  8. [[br2-external-converting]]
  9. === Migrating to 2016.11
  10. Before Buildroot 2016.11, it was possible to use only one br2-external
  11. tree at once. With Buildroot 2016.11 came the possibility to use more
  12. than one simultaneously (for details, see xref:outside-br-custom[]).
  13. This however means that older br2-external trees are not usable as-is.
  14. A minor change has to be made: adding a name to your br2-external tree.
  15. This can be done very easily in just a few steps:
  16. * First, create a new file named +external.desc+, at the root of your
  17. br2-external tree, with a single line defining the name of your
  18. br2-external tree:
  19. +
  20. ----
  21. $ echo 'name: NAME_OF_YOUR_TREE' >external.desc
  22. ----
  23. +
  24. .Note
  25. Be careful when choosing a name: It has to be unique and be made
  26. with only ASCII characters from the set +[A-Za-z0-9_]+.
  27. * Then, change every occurence of +BR2_EXTERNAL+ in your br2-external
  28. tree with the new variable:
  29. +
  30. ----
  31. $ find . -type f | xargs sed -i 's/BR2_EXTERNAL/BR2_EXTERNAL_NAME_OF_YOUR_TREE_PATH/g'
  32. ----
  33. Now, your br2-external tree can be used with Buildroot 2016.11 onward.
  34. .Note:
  35. This change makes your br2-external tree incompatible with Buildroot
  36. before 2016.11.
  37. [[migrating-host-usr]]
  38. === Migrating to 2017.08
  39. Before Buildroot 2017.08, host packages were installed in +$(HOST_DIR)/usr+
  40. (with e.g. the autotools' +--prefix=$(HOST_DIR)/usr+). With Buildroot
  41. 2017.08, they are now installed directly in +$(HOST_DIR)+.
  42. Whenever a package installs an executable that is linked with a library
  43. in +$(HOST_DIR)/lib+, it must have an RPATH pointing to that directory.
  44. An RPATH pointing to +$(HOST_DIR)/usr/lib+ is no longer accepted.