Testing GNOME Builder

Recently GNOME has released it’s new contribution workflow with GNOME Builder, an ideal IDE to develop GNOME applications. Even they build a completely new site to encourage newcomers to use this workflow. In this post I will follow the example of use that is showed in the link above.

First of all we need to have our system updated and running GNOME Shell 3.24 and GNOME Builder. We can check our version of shell running the command gnome-shell --version.

Once we have checked those dependencies we can run GNOME Builder.

Screenshot from 2017-04-29 20-47-28.png

Screenshot from 2017-04-29 20-50-58.png

I’m already use GNOME Builder (accidentally) and, as you can see, it has the capability to record your projects, specially if they are attached to a git repository.

With GNOME Builder open we can see that there is a button with the label clone. When you click on that button a simple menu is opened.

Screenshot from 2017-04-29 20-54-26.png

You need the repository url of the project you want to clone. You can find a complete list of GNOME project here. In this case I selected GNOME Polari , just as I said at the begin of this post. After copy and paste the url of GNOME Polari I press the button clone in the corner and the project is cloned!

Screenshot from 2017-04-29 20-57-43.png

After clone is complete the editor view of GNOME Builder is displayed. You can navigate through the directory tree check system monitor, the terminal, and build your project.

Screenshot from 2017-04-29 21-00-29.png

Clicking in the build your project label you can see that some packages are downloaded. Those package are part of GNOME runtime. As you see in the image below, when the top bar is clicked a simple panel is shown with  information about build profiles.

Screenshot from 2017-04-29 21-03-46.png

In this case I started building the project with Polari unstable profile. Sadly this mode got me two warnings, one error and a failed build.

Screenshot from 2017-04-29 21-11-22

The fatal error was due to an issue with eu-strip component. You can find more information regarded to this issue in this links:

  1. https://dev.solus-project.com/T2964
  2. https://github.com/flatpak/flatpak/issues/648

Happily the default mode (with the dependencies of my system) works like a charm!

Screenshot from 2017-04-29 21-19-50.png

Screenshot from 2017-04-29 21-21-26.png

And that’s all! Easy and fast for a first attempt and ideal for newcomers.

Meanwhile, I’m working for a solution with the problem that I pointed above. I hope to find a solution soon.

 

 

 

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s