ac337dab5b
The suite is quick, it takes ~5 seconds on my machine to execute. The tests consist of 2 or 3 parts, depending on how one counts them. The apitest PACKAGACONFIG compiles tests for the c-interface, as part of the main meson build. This apitest expects test data to be present in a folder relative the test binary: ../../rsvg/tests folder. ptest-cargo compiles two sets of test: rsvg-convert tests, and generic assorted tests for the library, in multiple binaries. The rsvg-convert tests expect test data to be present in a "tests" folder, in the same folder where the test binaries are. The library tests expect the tests to be in a folder called "tests", that's location is specified by the CARGO_MANIFEST_DIR environment variable. As part of compiling the cargo tests, rsvg-convert is also compiled specifically for the tests, however it is not supposed to be different from the actual binary. It is deleted from the test set, because of two reasons: 1. It is not bit-identical to the actually installed rsvg-convert (it is compiled differently, with cargo only, without meson) 2. ptest-cargo class treated it as a test binary, and tried to execute it, which resulted in failing/hanging test. It is avoided by not installing this binary, but rather use the real rsvg package as a runtime dependency, and create a symlink to it in the run-ptest script. Added liberation-fonts as a runtime dependency to the tests - the rsvg-convert tests require some fonts to be available to be able to render during some svg->pdf conversion tests. (From OE-Core rev: 3aee16beac9b12403babfc7eef02be71b2297e70) Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.