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 777283 - Set parameters for executing the binary of a project
Set parameters for executing the binary of a project
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: preferences
3.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-01-15 19:30 UTC by Peter Sonntag
Modified: 2018-01-11 10:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Peter Sonntag 2017-01-15 19:30:40 UTC
It would be helpful if there is the possibility to set parameters in the project preferences which are passed to the binary when it is executed.

Like "example -i test"
Comment 1 Christian Hergert 2017-01-17 21:21:46 UTC
This would indeed be nice to have.
Comment 2 Peter Sonntag 2017-01-17 21:55:52 UTC
Maybe there could be an additional option, like ask always before execution.
When executing the project this would bring up a text box for entering the parameters, prefilled with the last ones.
This would make it easier to try different parameters while debugging.
Comment 3 Christian Hergert 2017-01-17 22:07:34 UTC
(In reply to Peter Sonntag from comment #2)
> Maybe there could be an additional option, like ask always before execution.

I mean this in the politest way possible: No. :)

> When executing the project this would bring up a text box for entering the
> parameters, prefilled with the last ones.

We do eventually need UI for selecting the IdeBuildTarget to execute. Currently, we just try to discover the most likely one. I imagine we'll extend that UI for custom arguments. But I'd like to see this persisted to the underlying IdeConfiguration (or similar).

> This would make it easier to try different parameters while debugging.

Testing with a wide variety of input is probably best left to the command line or by the executing application asking for input. I'd rather avoid complicating Builder's UI for a small percentage of use cases when the terminal is an equally good UI.
Comment 4 Peter Sonntag 2017-01-18 07:01:12 UTC
I understand your point.
As I'm not that experienced, could you give me an hint where the binary is? I was not able to find it.
Comment 5 Christian Hergert 2017-01-18 07:04:26 UTC
We try to do builds out-of-tree by default, so they will be in a directory like ~/.cache/gnome-builder/builds/$project/$runtime/$device/.

It would be nice if we had a variable to simplify jumping there, like $builddir or something.
Comment 6 Peter Sonntag 2017-01-18 20:19:02 UTC
Maybe a stupid idea, but what about a symlink?
Comment 7 Christian Hergert 2017-01-18 20:29:29 UTC
It's essentially the same problem that this (long) thread discusses.

https://mail.gnome.org/archives/desktop-devel-list/2016-February/msg00070.html

Coming up with a good strategy wasn't exactly clear.
Comment 8 Christian Hergert 2017-11-27 04:54:57 UTC
For posterity, we do support run arguments when using flatpak. You can set the "x-run-args" parameter in the .json flatpak manifest.

We still need something better once we have some real project manipulation infrastructure.
Comment 9 GNOME Infrastructure Team 2018-01-11 10:15:57 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/168.