Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 317
    • Issues 317
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 119
    • Merge requests 119
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #29

Closed
Open
Created Jul 12, 2013 by Bugzilla Migration User@bugzilla-migration

weston-launch support specifing a binary path to another Wayland server

Submitted by ner..@..on.net

Assigned to Wayland bug list

Link to original bug (#66853)

Description

Hi.

Right now, weston-launch is only hard coded to launch weston.

I would really find an option to specify a path to another binary, with something such as weston-launch -b qtcompositor.

As there are other non weston compositors out there, not all of them ship with an equivilent of weston-launch that changes permissions as far as I'm aware.

Without much luck, I tried making a patch myself... http://pastebin.com/FRsK4DP6 but it doesn't work

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking