<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> We've successfully used cairo in an iOS app that was available in the appstore for several years. There is nothing in Apple appstore TOS that prevents one from using cairo (or any other such library), and we passed multiple appstore reviews without issues directly related to library use. However, cairo support for iOS was tenuous at best. In particular, there was never an official optimized pixman release (using ARM optimizations), ostensibly because it was designed for Android/Linux toolchain and there was no one interested in taking on a proper port to iOS toolchain. There was a one-off prebuilt set of ARM optimizations for a 32 bit platform, that we've used for a while. In addition, due to the way Quartz backend was built in older versions, it required a use of certain hacks to avoid referencing deprecated API. This was presumably remediet in later versions of cairo, unfortunately they had several other regressions and we never moved to newer version at that time. Since iOS now requires all applications to support 64 bit platform, and there is no corresponding optimized pixman version for 64 bit ARM (same issues as previously for 32 bit), we were only able to build a non-optimized 64 bit cairo/pixman combination for iOS. The resulting product performance was inadequate and stability suffered, so it was not made production - and application was subsequently withdrawn last year. I.e., in my experience, cairo can be built for iOS with non-trivial effort. The resulting library will be constrained in both performance and stability compared to other officially supported platform versions. Guillermo Rodriguez wrote: <blockquote cite="mid:CABDcavYTX_R9YLb2a2HH0HvPN4wETyt+PisBTpb4+Q8mAk05UA@mail.gmail.com" type="cite"> <pre wrap="">2017-01-20 10:32 GMT+01:00 Lawrence D'Oliveiro <a class="moz-txt-link-rfc2396E" href="mailto:ldo@geek-central.gen.nz"><ldo@geek-central.gen.nz></a>: </pre> <blockquote type="cite"> <pre wrap="">On Fri, 20 Jan 2017 09:42:02 +0100, Guillermo Rodriguez wrote: </pre> <blockquote type="cite"> <pre wrap="">2017-01-19 21:17 GMT+01:00 Lawrence D'Oliveiro: </pre> <blockquote type="cite"> <pre wrap="">On Thu, 19 Jan 2017 11:45:48 +0100, Guillermo Rodriguez Garcia wrote: </pre> </blockquote> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Why wouldn't it be allowed? </pre> </blockquote> <pre wrap="">Because Apple. </pre> </blockquote> <pre wrap="">If you want to make a point, you may want to be more specific. </pre> </blockquote> <pre wrap="">“Other reasons” (42% of rejections) <a class="moz-txt-link-rfc2396E" href="http://arstechnica.com/apple/2014/09/apple-lays-out-the-most-common-reasons-for-app-store-rejections/"><http://arstechnica.com/apple/2014/09/apple-lays-out-the-most-common-reasons-for-app-store-rejections/></a>. </pre> </blockquote> <pre wrap=""> As I said they may reject any application arbitrarily, but there is nothing in the link you provided that would suggest that specifically using Cairo would result in an application being rejected. Guillermo </pre> </blockquote> </body> </html>