Meson-UI should be able to handle cross-compile based projects. As new feature support should be added for the cross-file flag.

Meson API requires a reference page so other developers if any can use it to implement a new feature in Meson-UI.

I suppose that if I expose an API for Meson build projects maybe it would simplify implementing IDE backends.

Meson-UI should show notifications to show if a background command successfully runs or failed.

This is reasonable because it's hard enough to guess what's going on as it is.

It would be good to add GNOME to the backend library.

JetBrains has a family of tools that share similar common ideas such as .idea for storing project files.

My idea of what a family is in this context is a common interface for backends created by those developers like cline, IntelliJ, android, or even eclipse. This should go in the backends/family directory.

Normally on Windows, you need to launch the configuration process from the Visual Studio developer command prompt. Visual Studio requires a bunch of environment variables & other settings to work.

I would like to implement some way to provide those variables to make it easier for Meson build system users to go about there day using Visual Studio.

The Meson build system seems to have changed how buildtype and optimization work, so time to update the code to accommodate for that.

WARNING: Recommend using either -Dbuildtype or -Doptimization + -Ddebug. Using both is redundant since they override each other. See: https://mesonbuild.com/Builtin-options.html#build-type-options

I think Meson-UI should have custom backends for IDEs like eclipse, qtcreator, kdevelop, and more. This feature should extend the currently existing list of backends provided from the Meson build system.

Here are some IDEs I'm hoping to get added to the list.

'eclipse', 'qtcreator', 'kdevelop', 'gnome', 'codeblocks', 'cline'

As a suggestion for implementation, I am considering a backend factory.

I would consider implementing a version of a visual studio backend collection that didn’t require any extra setup steps as part of the Meson-UI backend library.

Also to remove the dependency for using Meson build system version of visual studio backends.

Possible names are the following:

• vs Autodidact Visual Studio
• vsmac Visual Studio for Mac
• vs2010 Visual Studio 2010
• vs2012 Visual Studio 2012
• vs2013 Visual Studio 2013
• vs2015 Visual Studio 2015
• vs2017 Visual Studio 2017
• vs2019 Visual Studio 2019

I would love to provide Meson-UI to all snap app shoppers. The benefit of this would be to cover more Linux distros including those that can't support Python36.

Adding a GitHub action to help update the Linux images if thy change will be helpful. Mostly if the plan is to keep expanding on the Dockerfile collection.

Describe the bug
Meson-UI fails to perform Meson commands in user project source root directory.

To Reproduce
N/A

Expected behavior
I expect to have Meson commands run in a user-defined directory, not in the application root directory.

system parameters

• MacOS Catalina
• Python version 3.8.2
• meson-ui version 0.20.0 beta
• meson version 0.53.999
• ninja version 1.10.0

Seems Meson-UI is not reading Meson introspection API fresh from build directories.

May need to fix that before doing anything else related to setting and configuration in Meson-UI.

Introspection dashboard doesn’t seem to load anything. Should be fixed before the release.

I think it would help if Meson-UI have basic support for CMake based projects. Meson-UI's should be able to do this by scanning for the build script in root directory, default setting will be Meson build.

I understand not everyone will jump onto the Meson build GUI bandwagon and tend to find the command line easier to work with. As a response to that, I'm hoping to have cmeson created for those users from the world of curses.

The cmeson project will be a curses version of Meson-UI that can be invoked and used from within the terminal. The name of the project is solely based on CMake ccmake.

Example for running this should be something like the following:

cmeson 

Adding Mint-Linux to the existing collection of docker files will help with expanding support for mutable distributions of Linux. To do so with a new Dockerfile for the distro.

IDE backends require a reference page so other users can see what backends are supported and if it's supported from Meson build system or Meson-UI.

Adding CentOS to the existing collection of docker files will help with expanding support for mutable distributions of Linux. To do so with a new Dockerfile for the distro.