Re: Splitting the cairo backends up so they can be in separate packages?
Stuart Axon <[email protected]> Fri, 6 Dec 2019 17:13:31 +0000 (UTC)
| Newsgroups | gmane.comp.lib.cairo |
|---|---|
| Message-ID | <[email protected]> |
--===============1763756184==
Content-Type: multipart/alternative;
boundary="----=_Part_4467938_767386276.1575652411415"
------=_Part_4467938_767386276.1575652411415
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[Apologies for missing the end of my mail out]
The end goal would be to separately package the backends - so if you just want an image or pdf backend, you wouldn't need to have xlib installed just to install cairo.
S++
On Friday, December 6, 2019, 5:02:13 PM GMT, Stuart Axon <[email protected]> wrote:
I was wondering how hard it would be to split up cairo by backend, would it be feasible to build it so there instead of libcairo.so, there is libcairo-${backend}.so, e.g.
libcairo-image.so
libcairo-xcb.solibcairo-pdf.so
etc..?
Any idea what I would need to change to make it build like this ?
(Also, any problems that could arise).
If it could be split up, these could be packaged separately, so if you just want the image backend, you wouldn't need.
------=_Part_4467938_767386276.1575652411415
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html><head></head><body><div class="ydp9aa71263yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div><div dir="ltr" data-setdir="false">[Apologies for missing the end of my mail out]</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">The end goal would be to separately package the backends - so if you just want an image or pdf backend, you wouldn't need to have xlib installed just to install cairo.<br></div><div><br></div><div class="ydp9aa71263signature">S++</div></div>
<div><br></div><div><br></div>
</div><div id="yahoo_quoted_6362709844" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, December 6, 2019, 5:02:13 PM GMT, Stuart Axon <[email protected]> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv0855228874"><div><div class="yiv0855228874ydpb56edbefyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;" dir="ltr"><div dir="ltr">I was wondering how hard it would be to split up cairo by backend, would it be feasible to build it so there instead of libcairo.so, there is libcairo-${backend}.so, e.g.</div><div dir="ltr"><br></div><div dir="ltr">libcairo-image.so<br></div><div dir="ltr">libcairo-xcb.so</div><div dir="ltr">libcairo-pdf.so</div><div dir="ltr"><br></div><div dir="ltr">etc..?</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Any idea what I would need to change to make it build like this ?</div><div dir="ltr"><br></div><div dir="ltr">(Also, any problems that could arise).<br></div
><div dir="ltr"><br></div><div dir="ltr">If it could be split up, these could be packaged separately, so if you just want the image backend, you wouldn't need.</div></div></div></div></div>
</div>
</div></body></html>
------=_Part_4467938_767386276.1575652411415--
--===============1763756184==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
LS0gCmNhaXJvIG1haWxpbmcgbGlzdApjYWlyb0BjYWlyb2dyYXBoaWNzLm9yZwpodHRwczovL2xp
c3RzLmNhaXJvZ3JhcGhpY3Mub3JnL21haWxtYW4vbGlzdGluZm8vY2Fpcm8=
--===============1763756184==--