Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #816

Closed
Open
Created Jun 07, 2018 by anna@anna

Migration to Meson Build system

As the meson webpage (https://mesonbuild.com) says:

"Meson is an open source build system meant to be both extremely fast, and, even more importantly, as user friendly as possible.

The main design point of Meson is that every moment a developer spends writing or debugging build definitions is a second wasted. So is every second spent waiting for the build system to actually start compiling code."

This migration is encouraged by GNOME project development goals: https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting

Still not sure if this just affects GNOME client or https://git.ring.cx/savoirfairelinux/ring-project.git as well, cause several Ring projects use cmake (LRC, OpenDHT, GNOME client). Others Ring projects that use autotools for now could be ported too.

https://mesonbuild.com/Porting-from-autotools.html#porting-from-autotools as Meson seems to support macOS, iOS, Android and Windows.

What do you think?

Assignee
Assign to
Time tracking