|
@@ -45,7 +45,7 @@ continuously test random configurations. However, these only build the
|
|
|
`master` branch of the git tree, and your new fancy package is not yet
|
|
|
there.
|
|
|
|
|
|
-Buildroot provides a script in +tools/test-pkg+ that uses the same base
|
|
|
+Buildroot provides a script in +utils/test-pkg+ that uses the same base
|
|
|
configurations as used by the autobuilders so you can test your package
|
|
|
in the same conditions.
|
|
|
|
|
@@ -74,7 +74,7 @@ Then run the +test-pkg+ script, by telling it what config snippet to use
|
|
|
and what package to test:
|
|
|
|
|
|
----
|
|
|
-$ ./tools/test-pkg -c libcurl.config -p libcurl
|
|
|
+$ ./utils/test-pkg -c libcurl.config -p libcurl
|
|
|
----
|
|
|
|
|
|
This will try to build your package against all the toolchains used
|
|
@@ -83,7 +83,7 @@ too long to do so). The output lists all toolchains and the corresponding
|
|
|
result (excerpt, results are fake):
|
|
|
|
|
|
----
|
|
|
-$ ./tools/test-pkg -c libcurl.config -p libcurl
|
|
|
+$ ./utils/test-pkg -c libcurl.config -p libcurl
|
|
|
armv5-ctng-linux-gnueabi [ 1/11]: OK
|
|
|
armv7-ctng-linux-gnueabihf [ 2/11]: OK
|
|
|
br-aarch64-glibc [ 3/11]: SKIPPED
|
|
@@ -124,7 +124,7 @@ The +test-pkg+ script accepts a few options, for which you can get some
|
|
|
help by running:
|
|
|
|
|
|
----
|
|
|
-$ ./tools/test-pkg -h
|
|
|
+$ ./utils/test-pkg -h
|
|
|
----
|
|
|
|
|
|
[[github-download-url]]
|