translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
library
    Bellagio OpenMAX IL0.9.3
    QmTZVRfzPWbamQE2ufWB61yiNv78JPLk1cKZHQkuheK1S5
    5ds5VkUvR6URsLYbogdKYHQbMyMXQk
      QmTZVRfzPWbamQE2ufWB61yiNv78JPLk1cKZHQkuheK1S5
      5ds5VkUvR6URsLYbogdKYHQbMyMXQk

      • Details
      • Build
      • Files
      • History
        • Summary

          An open-source implementation of the OpenMAX Integration Layer.

          Environment

          linux

          Architecture

          x86-64

          Versions

          • 0.9.3

          Related

          • maintainer

            occam

          Includes

          • application

            omxregister-bellagio

          BuildHelp

          This section tracks information useful to describing how to build this object.

          Dependencies

          • collection

            build

            1.0

          • compiler

            g++

            5.x

          • application

            m4

            1.x

          • collection

            gettext

            0.19.x

          • collection

            autoconf

            2.x

          • collection

            automake

            1.x

          • application

            libtool

            2.x

          • application

            patch

            2.x

          Resources

          • libomxil-bellagio-0.9.3.tar.gz

            application/gzip

            Bellagio OpenMAX IL 0.9.3 Source Code

            https://downloads.sourceforge.net/project/omxil/omxil/Bellagio%200.9.3/libomxil-bellagio-0.9.3.tar.gz

            QmQaMrw1FRRYG8UTvgkSG2zLjuHNsb17JmzxsDgfchobS9

            QmRGw2t5x7nF9N9hRy3Nsjvc9awFabBcTfKD1rtcxTzwqf

            QmULz5onVJJ5eRtZE9e7KyS8x23hzQmHNjHwYi4Anwq64j

            download

          Command

          • /bin/bash
          • build.sh

          Build Environment

          • linux
          • x86-64

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Linkusr/lib/usr/lib

          N/A

          Linkusr/bin/usr/bin

          N/A

          Linkusr/share/usr/share

          N/A

          Linkusr/include/usr/include

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?