Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M meta-intel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • automation
  • so
  • mirror
  • meta-intel
  • Repository
  • meta-intel
  • classes
  • emgd-gl.bbclass
Find file Blame History Permalink
  • Richard Purdie's avatar
    Separate packagedir for GL components of EMGD BSPs · 49f495e3
    Richard Purdie authored Sep 16, 2013
    
    
    When multiple BSPs of the same arch are built in a build directory,
    the differences in GL providers such as emgd-driver and mesa causes
    rebuild of large set of recipes, as they collide on each other's space
    for multiple BSPs. Although this does not impact correctness, it
    impacts build performance negatively.
    
     Richard had an idea of providing separate PACKAGE_DIR to the
    colliding recipes to avoid the build area collision. And this approach
    significantly reduces the negative impact on the build performance.
    
    Signed-off-by: default avatarNitin A Kamble <nitin.a.kamble@intel.com>
    Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
    49f495e3