<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-graphics/cairo, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-11-07T13:31:53+00:00</updated>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T13:31:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c22ff0d8b70d9b12f0487ef696a7e915b9e3173'/>
<id>urn:sha1:8c22ff0d8b70d9b12f0487ef696a7e915b9e3173</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta: remove consecutive blank lines</title>
<updated>2025-06-20T11:07:27+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-06-16T09:50:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dc9faa3cdc057983b55fb6bd19091722c58bc62c'/>
<id>urn:sha1:dc9faa3cdc057983b55fb6bd19091722c58bc62c</id>
<content type='text'>
Some of them were introduced by mass-removal of S = WORKDIR/git assignments;
rather than try to fix up (or redo) just these, I've run this sed command over
the whole tree:

sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc`

The rationale is that more than one empty line is wasting vertical screen space, and
does nothing for readability.

(From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: upgrade 1.18.2 -&gt; 1.18.4</title>
<updated>2025-03-17T22:38:32+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-03-15T11:55:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=50d69d9ab65c3a7ad72f935a72f3a728f3db0987'/>
<id>urn:sha1:50d69d9ab65c3a7ad72f935a72f3a728f3db0987</id>
<content type='text'>
(From OE-Core rev: 36cde7319bbdc2d4d69ea9cc8f54045c1c4e106b)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: disable some features explicitly</title>
<updated>2024-11-12T11:31:48+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-11-11T18:13:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0c3802cbea770d2b472c94355dfb86123e6173a0'/>
<id>urn:sha1:0c3802cbea770d2b472c94355dfb86123e6173a0</id>
<content type='text'>
These are disabled out of the box but only because the dependencies are
not present. Explicitly disable them to be clear.

(From OE-Core rev: 6efa5d5ae086f7178b3f7516803f24c78274bba1)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: upgrade 1.18.0 -&gt; 1.18.2</title>
<updated>2024-09-04T11:38:44+00:00</updated>
<author>
<name>Wang Mingyu</name>
<email>wangmy@fujitsu.com</email>
</author>
<published>2024-09-03T08:32:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=de0f9cdbe16fc7e9a42522434b8c0a6fec510134'/>
<id>urn:sha1:de0f9cdbe16fc7e9a42522434b8c0a6fec510134</id>
<content type='text'>
Changelog:
===========
- The malloc-stats code has been removed from the tests directory
  Cairo now requires a version of pixman equal to, or newer than, 0.40.
- There have been multiple build fixes for newer versions of GCC
  for MSVC; for Solaris; and on macOS 10.7
- PNG errors caused by loading malformed data are correctly propagated to
  callers, so they can handle the case.
- Both stroke and fill colors are now set when showing glyphs on a PDF
  surface.
- All the font options are copied when creating a fallback font object.
- When drawing text on macOS, Cairo now tries harder to select the appropriate
  font name.
- Cairo now prefers the COLRv1 table inside a font, if one is available.
- Cairo requires a C11 toolchain when building.

(From OE-Core rev: 070d79c8adec7e0a8862019cf61910a59b18613a)

Signed-off-by: Wang Mingyu &lt;wangmy@fujitsu.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nativesdk-cairo: fix build error</title>
<updated>2024-01-26T16:06:29+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2024-01-22T09:56:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dba0b9044663853f30621bad999420df4428d216'/>
<id>urn:sha1:dba0b9044663853f30621bad999420df4428d216</id>
<content type='text'>
It fails to build nativesdk-cairo:

| ../cairo-1.18.0/meson.build:381:13: ERROR: Can not run test
    applications in this cross environment.

Set meson property ipc_rmid_deferred_release in cross-file to fix the
issue which is as same as for target cairo

(From OE-Core rev: e7388c4b351baa56be596af405730c8626b572da)

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: upgrade to 1.18.0</title>
<updated>2024-01-12T11:54:05+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-01-10T21:01:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ef9f8330c1b85325969f76bc97272905eeedd5e0'/>
<id>urn:sha1:ef9f8330c1b85325969f76bc97272905eeedd5e0</id>
<content type='text'>
The changelog is large[1] but:

Added:
- Type 3 colour and COLRv2 fonts
- Tee surfice automatically enabled
- Meson build system

Removed:
- The cairo-sphinx tool
- The XML, GL, GLES, Qt5, BeOS, OS/2, DirectFB, DRM, Cogl, and OpenVL
  backends
- Autotools build system

These CVE patches have been merged upstream:
  CVE-2018-19876.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/90e85c2493fdfa3551f202ff10282463f1e36645
  CVE-2019-6461.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/09643ee1abdd5daacebfcb564448f29be9a79bac
  CVE-2019-6462.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/bbeaf08190d3006a80b80a77724801cd477a37b8
  CVE-2020-35492.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/c986a7310bb06582b7d8a566d5f007ba4e5e75bf

Some niche options have been removed in the migration to Meson, so the
recipe can be cleaned up.

Put libcairo-fdr ("flight data recorder") in the perf-utils package
instead of deleting it.

There is an executable test for IPC behaviour that needs to be set via a
cross file if qemu-user isn't available, thanks to Alex Kanavin for this
portion.

[1] https://www.cairographics.org/news/cairo-1.18.0/

(From OE-Core rev: 9a4ca6b08d6031ebb67adcdd650aa59acd4fb5fb)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: fix CVE patches assigned wrong CVE number</title>
<updated>2023-01-06T12:03:47+00:00</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@theobroma-systems.com</email>
</author>
<published>2023-01-02T14:39:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=99b4356b3507f204749124f89cf3217b45882031'/>
<id>urn:sha1:99b4356b3507f204749124f89cf3217b45882031</id>
<content type='text'>
CVE-2019-6461 and CVE-2019-6462 are fixed, but the reporting is
incorrect as the patch for CVE-2019-6461 is actually for CVE-2019-6462
and vice-versa.

This swaps both files and edit the CVE field to report the correct
identifier.

Cc: Quentin Schulz &lt;foss+yocto@0leil.net&gt;
(From OE-Core rev: f12c2a5ac94cb29f473f3c7e335463c7fb6d8a6e)

Signed-off-by: Quentin Schulz &lt;quentin.schulz@theobroma-systems.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: update patch for CVE-2019-6461 with upstream solution</title>
<updated>2022-12-17T23:49:56+00:00</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@theobroma-systems.com</email>
</author>
<published>2022-12-13T15:53:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=caed08fe897dbda53151a6a7789dc6c38ccb4817'/>
<id>urn:sha1:caed08fe897dbda53151a6a7789dc6c38ccb4817</id>
<content type='text'>
Upstream went with something slightly different so let's update the
patch so we don't have to carry a patch that isn't going to be merged.

This patch is part of snapshot 1.17.6.

Cc: Quentin Schulz &lt;foss+yocto@0leil.net&gt;
(From OE-Core rev: 19eb1e388fbbe5bfb8462710c745f2bb5446b5b5)

Signed-off-by: Quentin Schulz &lt;quentin.schulz@theobroma-systems.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cairo: Adapt the license information based on what is being built</title>
<updated>2022-09-08T13:59:39+00:00</updated>
<author>
<name>Peter Kjellerstedt</name>
<email>peter.kjellerstedt@axis.com</email>
</author>
<published>2022-09-06T13:33:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ed3db56c496d4320dc86960843d84bf4d44b3279'/>
<id>urn:sha1:ed3db56c496d4320dc86960843d84bf4d44b3279</id>
<content type='text'>
If the "trace" PACKAGECONFIG is removed to disable cairo-trace (the
only part of the code licensed as GPL-3.0), we can adapt the licenses
for cairo-dbg and cairo-src so that they do not include
"GPL-3.0-or-later" and thus they can be used also when, e.g., GPL-3.0
is blacklisted in INCOMPATIBLE_LICENSE. Also drop the GPL-3.0 license
text from LIC_FILES_CHKSUM in this case.

(From OE-Core rev: 4f0ea44c80f297d00349b7d3cf9438145aec8a74)

Signed-off-by: Peter Kjellerstedt &lt;peter.kjellerstedt@axis.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
