Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pitivi pitivi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 194
    • Issues 194
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • pitivipitivi
  • Merge requests
  • !354

Draft: docs: Add development environment setup under WSL.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Brady Garvin requested to merge brady.j.garvin/pitivi:wsl_instructions into master Jan 28, 2021
  • Overview 0
  • Commits 1
  • Pipelines 4
  • Changes 4

This is a work-in-progress MR documenting how to create a Pitivi development environment by running Ubuntu 20.04 or a similar distro under Windows Subsystem for Linux (WSL).

Questions on the process itself:

  • I'm betting that Step 11 could be better since the OS's libgstpulseaudio.so might be old. Are there options for building a .so providing the pulsesink element in the gst-build environment? Similar questions apply to the other three plugins that some students needed symlinked to get the test cases passing.

  • It seems surprising that Step 12 is necessary, especially since the data/pixmaps is added to the Yaru icon theme's search path when I enter the gst-build environment. Did I overlook something earlier?

  • In Step 13, I am copying and patching the pre-commit hook instead of symlinking it. Obviously it would be better to submit an MR to make the hook work under WSL by default, but I wanted to get your opinions and first make sure that looking for pre-commit with which is safe under all environments. The blame suggests that care might be required with GNOME Builder, which I have not used. If the hook can't be symlinked, then the first paragraph in …/docs/Precommit_hooks.md should probably acknowledge that that the hook could actually be a copy.

Questions on the documentation:

  • Should crossplatform.md link to WSL.md?

  • If so, should WSL.md be under HACKING.md or crossplatform.md in sitemap.txt?

Edited Mar 19, 2021 by Brady Garvin
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: wsl_instructions