After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781052 - gnome-builder chooses incorrect build system when building gnome-polari (master)
gnome-builder chooses incorrect build system when building gnome-polari (master)
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
Flatpak Stable Channel
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-04-08 12:27 UTC by Sebastian Rasmussen
Modified: 2018-01-11 10:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Rasmussen 2017-04-08 12:27:51 UTC 
When building gnome-polari (master, commit 6818d86) gnome-builder chose to use meson and so it failed with "meson: error: unrecognized arguments: --disable-static"

After some discussion with csoriano on #gnome-builder he concluded that gnome-builder is choosing the incorrect build system (it should be using autotools as the mast manifest uses this build system). If I instead choose the unstable manifest then everything builds correctly (since this indeed uses the meson build system).
Comment 1 Carlos Soriano 2017-04-08 12:29:49 UTC 
Probably the right thing to do is to not have multiple manifest per code tree, and make them per branch. Unfortunately seems the wiki indicates the opposite https://wiki.gnome.org/Projects/SandboxedApps/Building .

In any case, I guess we want to make Builder more reliable against these issues anyway.
Comment 2 Christian Hergert 2017-04-08 19:15:40 UTC 
We don't have a clean way to solve this until we get to some sort of notion of "Solutions".

I agree that different build systems in different json files is a bad idea and should be kept to branches.
Comment 3 GNOME Infrastructure Team 2018-01-11 10:25:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/217.