Cairos's configure output: Is it enough for Firefox?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












I intend to compile Firefox from the source. For that, I do need to compile GTK. And for that, I do need to compile Cairo.



After solving some of Cairo's dependencies, I was able to run the configure script. Bellow, the result:



cairo (version 1.10.2 [release]) will be compiled with:

The following surface backends:
Image: yes (always builtin)
Recording: yes (always builtin)
Tee: no (disabled, use --enable-tee to enable)
XML: no (disabled, use --enable-xml to enable)
Skia: no (disabled, use --enable-skia to enable)
Xlib: yes
Xlib Xrender: no (requires http://freedesktop.org/Software/xlibs)
Qt: no (disabled, use --enable-qt to enable)
Quartz: no (requires CoreGraphics framework)
Quartz-image: no (disabled, use --enable-quartz-image to enable)
XCB: no (disabled, use --enable-xcb to enable)
Win32: no (requires a Win32 platform)
OS2: no (disabled, use --enable-os2 to enable)
CairoScript: no (disabled, use --enable-script to enable)
PostScript: yes
PDF: yes
SVG: yes
OpenGL: no (disabled, use --enable-gl to enable)
BeOS: no (disabled, use --enable-beos to enable)
DirectFB: no (disabled, use --enable-directfb to enable)
OpenVG: no (disabled, use --enable-vg to enable)
DRM: no (disabled, use --enable-drm to enable)

The following font backends:
User: yes (always builtin)
FreeType: no (freetype-config not found in path or $FREETYPE_CONFIG)
Fontconfig: no (freetype-config not found in path or $FREETYPE_CONFIG)
Win32: no (requires a Win32 platform)
Quartz: no (requires CoreGraphics framework)

The following functions:
PNG functions: yes
GLEW functions: no (not required by any backend)
GLX functions: no (not required by any backend)
WGL functions: no (not required by any backend)
EGL functions: no (not required by any backend)
X11-xcb functions: no (disabled, use --enable-xlib-xcb to enable)
XCB-drm functions: no (disabled, use --enable-xcb-drm to enable)
XCB-shm functions: no (requires --enable-xcb)
DRM-Xr functions: no (disabled, use --enable-drm-xr to enable)

The following features and utilities:
cairo-trace: yes
cairo-script-interpreter: yes

And the following internal features:
pthread: yes
gtk-doc: no
gcov support: no
symbol-lookup: no (requires bfd)
test surfaces: no (disabled, use --enable-test-surfaces to enable)
ps testing: no (requires libspectre)
pdf testing: no (requires poppler-glib >= 0.13.3)
svg testing: no (requires librsvg-2.0 >= 2.15.0)


*** No native font backends enabled for your platform. It is strongly
*** recommended that you enable the native font backend feature for your
*** platform.


I am asking that mainly due to the warn above. Are those FreeType, FontType or Quartz really necessary (having Firefox in mind)? Anything else that would be nice to have? Thanks for the input.










share|improve this question

























    up vote
    1
    down vote

    favorite
    1












    I intend to compile Firefox from the source. For that, I do need to compile GTK. And for that, I do need to compile Cairo.



    After solving some of Cairo's dependencies, I was able to run the configure script. Bellow, the result:



    cairo (version 1.10.2 [release]) will be compiled with:

    The following surface backends:
    Image: yes (always builtin)
    Recording: yes (always builtin)
    Tee: no (disabled, use --enable-tee to enable)
    XML: no (disabled, use --enable-xml to enable)
    Skia: no (disabled, use --enable-skia to enable)
    Xlib: yes
    Xlib Xrender: no (requires http://freedesktop.org/Software/xlibs)
    Qt: no (disabled, use --enable-qt to enable)
    Quartz: no (requires CoreGraphics framework)
    Quartz-image: no (disabled, use --enable-quartz-image to enable)
    XCB: no (disabled, use --enable-xcb to enable)
    Win32: no (requires a Win32 platform)
    OS2: no (disabled, use --enable-os2 to enable)
    CairoScript: no (disabled, use --enable-script to enable)
    PostScript: yes
    PDF: yes
    SVG: yes
    OpenGL: no (disabled, use --enable-gl to enable)
    BeOS: no (disabled, use --enable-beos to enable)
    DirectFB: no (disabled, use --enable-directfb to enable)
    OpenVG: no (disabled, use --enable-vg to enable)
    DRM: no (disabled, use --enable-drm to enable)

    The following font backends:
    User: yes (always builtin)
    FreeType: no (freetype-config not found in path or $FREETYPE_CONFIG)
    Fontconfig: no (freetype-config not found in path or $FREETYPE_CONFIG)
    Win32: no (requires a Win32 platform)
    Quartz: no (requires CoreGraphics framework)

    The following functions:
    PNG functions: yes
    GLEW functions: no (not required by any backend)
    GLX functions: no (not required by any backend)
    WGL functions: no (not required by any backend)
    EGL functions: no (not required by any backend)
    X11-xcb functions: no (disabled, use --enable-xlib-xcb to enable)
    XCB-drm functions: no (disabled, use --enable-xcb-drm to enable)
    XCB-shm functions: no (requires --enable-xcb)
    DRM-Xr functions: no (disabled, use --enable-drm-xr to enable)

    The following features and utilities:
    cairo-trace: yes
    cairo-script-interpreter: yes

    And the following internal features:
    pthread: yes
    gtk-doc: no
    gcov support: no
    symbol-lookup: no (requires bfd)
    test surfaces: no (disabled, use --enable-test-surfaces to enable)
    ps testing: no (requires libspectre)
    pdf testing: no (requires poppler-glib >= 0.13.3)
    svg testing: no (requires librsvg-2.0 >= 2.15.0)


    *** No native font backends enabled for your platform. It is strongly
    *** recommended that you enable the native font backend feature for your
    *** platform.


    I am asking that mainly due to the warn above. Are those FreeType, FontType or Quartz really necessary (having Firefox in mind)? Anything else that would be nice to have? Thanks for the input.










    share|improve this question























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      I intend to compile Firefox from the source. For that, I do need to compile GTK. And for that, I do need to compile Cairo.



      After solving some of Cairo's dependencies, I was able to run the configure script. Bellow, the result:



      cairo (version 1.10.2 [release]) will be compiled with:

      The following surface backends:
      Image: yes (always builtin)
      Recording: yes (always builtin)
      Tee: no (disabled, use --enable-tee to enable)
      XML: no (disabled, use --enable-xml to enable)
      Skia: no (disabled, use --enable-skia to enable)
      Xlib: yes
      Xlib Xrender: no (requires http://freedesktop.org/Software/xlibs)
      Qt: no (disabled, use --enable-qt to enable)
      Quartz: no (requires CoreGraphics framework)
      Quartz-image: no (disabled, use --enable-quartz-image to enable)
      XCB: no (disabled, use --enable-xcb to enable)
      Win32: no (requires a Win32 platform)
      OS2: no (disabled, use --enable-os2 to enable)
      CairoScript: no (disabled, use --enable-script to enable)
      PostScript: yes
      PDF: yes
      SVG: yes
      OpenGL: no (disabled, use --enable-gl to enable)
      BeOS: no (disabled, use --enable-beos to enable)
      DirectFB: no (disabled, use --enable-directfb to enable)
      OpenVG: no (disabled, use --enable-vg to enable)
      DRM: no (disabled, use --enable-drm to enable)

      The following font backends:
      User: yes (always builtin)
      FreeType: no (freetype-config not found in path or $FREETYPE_CONFIG)
      Fontconfig: no (freetype-config not found in path or $FREETYPE_CONFIG)
      Win32: no (requires a Win32 platform)
      Quartz: no (requires CoreGraphics framework)

      The following functions:
      PNG functions: yes
      GLEW functions: no (not required by any backend)
      GLX functions: no (not required by any backend)
      WGL functions: no (not required by any backend)
      EGL functions: no (not required by any backend)
      X11-xcb functions: no (disabled, use --enable-xlib-xcb to enable)
      XCB-drm functions: no (disabled, use --enable-xcb-drm to enable)
      XCB-shm functions: no (requires --enable-xcb)
      DRM-Xr functions: no (disabled, use --enable-drm-xr to enable)

      The following features and utilities:
      cairo-trace: yes
      cairo-script-interpreter: yes

      And the following internal features:
      pthread: yes
      gtk-doc: no
      gcov support: no
      symbol-lookup: no (requires bfd)
      test surfaces: no (disabled, use --enable-test-surfaces to enable)
      ps testing: no (requires libspectre)
      pdf testing: no (requires poppler-glib >= 0.13.3)
      svg testing: no (requires librsvg-2.0 >= 2.15.0)


      *** No native font backends enabled for your platform. It is strongly
      *** recommended that you enable the native font backend feature for your
      *** platform.


      I am asking that mainly due to the warn above. Are those FreeType, FontType or Quartz really necessary (having Firefox in mind)? Anything else that would be nice to have? Thanks for the input.










      share|improve this question













      I intend to compile Firefox from the source. For that, I do need to compile GTK. And for that, I do need to compile Cairo.



      After solving some of Cairo's dependencies, I was able to run the configure script. Bellow, the result:



      cairo (version 1.10.2 [release]) will be compiled with:

      The following surface backends:
      Image: yes (always builtin)
      Recording: yes (always builtin)
      Tee: no (disabled, use --enable-tee to enable)
      XML: no (disabled, use --enable-xml to enable)
      Skia: no (disabled, use --enable-skia to enable)
      Xlib: yes
      Xlib Xrender: no (requires http://freedesktop.org/Software/xlibs)
      Qt: no (disabled, use --enable-qt to enable)
      Quartz: no (requires CoreGraphics framework)
      Quartz-image: no (disabled, use --enable-quartz-image to enable)
      XCB: no (disabled, use --enable-xcb to enable)
      Win32: no (requires a Win32 platform)
      OS2: no (disabled, use --enable-os2 to enable)
      CairoScript: no (disabled, use --enable-script to enable)
      PostScript: yes
      PDF: yes
      SVG: yes
      OpenGL: no (disabled, use --enable-gl to enable)
      BeOS: no (disabled, use --enable-beos to enable)
      DirectFB: no (disabled, use --enable-directfb to enable)
      OpenVG: no (disabled, use --enable-vg to enable)
      DRM: no (disabled, use --enable-drm to enable)

      The following font backends:
      User: yes (always builtin)
      FreeType: no (freetype-config not found in path or $FREETYPE_CONFIG)
      Fontconfig: no (freetype-config not found in path or $FREETYPE_CONFIG)
      Win32: no (requires a Win32 platform)
      Quartz: no (requires CoreGraphics framework)

      The following functions:
      PNG functions: yes
      GLEW functions: no (not required by any backend)
      GLX functions: no (not required by any backend)
      WGL functions: no (not required by any backend)
      EGL functions: no (not required by any backend)
      X11-xcb functions: no (disabled, use --enable-xlib-xcb to enable)
      XCB-drm functions: no (disabled, use --enable-xcb-drm to enable)
      XCB-shm functions: no (requires --enable-xcb)
      DRM-Xr functions: no (disabled, use --enable-drm-xr to enable)

      The following features and utilities:
      cairo-trace: yes
      cairo-script-interpreter: yes

      And the following internal features:
      pthread: yes
      gtk-doc: no
      gcov support: no
      symbol-lookup: no (requires bfd)
      test surfaces: no (disabled, use --enable-test-surfaces to enable)
      ps testing: no (requires libspectre)
      pdf testing: no (requires poppler-glib >= 0.13.3)
      svg testing: no (requires librsvg-2.0 >= 2.15.0)


      *** No native font backends enabled for your platform. It is strongly
      *** recommended that you enable the native font backend feature for your
      *** platform.


      I am asking that mainly due to the warn above. Are those FreeType, FontType or Quartz really necessary (having Firefox in mind)? Anything else that would be nice to have? Thanks for the input.







      firefox configure gtk3






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 29 at 11:36









      user2752471

      164




      164

























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484884%2fcaiross-configure-output-is-it-enough-for-firefox%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484884%2fcaiross-configure-output-is-it-enough-for-firefox%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown






          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?