Is there a better way to run the app for development?

[devforgely]

Currently what I am doing to run the app after code changes:

1. meson setup builddir (only 1 time for configuration)
2. ninja -C builddir install
3. run ./builddir/src/sudokugame

What I do not get is why it is not set up so that during development, you can just do:

1. ninja -C builddir (this would update relevant resource files and put in bundle)
2. run ./builddir/src/sudokugame

Shouldn't the install command be only for deployment purpose?
Some disadvantages of this:

• creates duplicate files in /usr/local
• slows down the development workflow, since every change requires copying all files to pkgdatadir, even if only a few files were modified. There are no checks to avoid unnecessary copying.

Suggestion:

• using an environment variable or command-line flag to switch between development and installed resource locations.

I’m new to Meson and Ninja, so I might be missing something. If there’s an existing or recommended way to run the app easily during development, I’d appreciate any guidance or suggestions.

[sepehr-rs]

I'm sorry for not getting back to you sooner. I just noticed this again.

You’re right that ninja -C builddir is usually the standard development loop, and ninja install is mainly for deployment. Some GNOME projects handle resources differently, though, which is why you might see the extra copy/install step.

One option to simplify development is to use GNOME Builder, which takes care of running apps with the right runtime and data files without needing ninja install each time. That way, you can just hit Run and test changes immediately.

Here are some links that might help you:

1. GNOME Builder
2. Foundry