Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gnome-terminal
gnome-terminal
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GNOME
  • gnome-terminalgnome-terminal
  • Issues
  • #227

Closed
Open
Opened Mar 04, 2020 by Alberto Ruiz@aruizDeveloper

Meson as a build system

I am working on a meson port that is a clean room implementation wrt previous efforts, everything is squashed into one commit.

Here is the branch: https://gitlab.gnome.org/aruiz/gnome-terminal/-/tree/wip/meson Here is a merge request in my own fork for convenience: aruiz/gnome-terminal!2 (diffs)

I am looking for feedback from people who have more experience on the yelp and i18n side of the port as I am not entirely sure I did the right thing there.

Edited Mar 05, 2020 by Alberto Ruiz
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gnome-terminal#227