New version of Ubuntu SDK IDE ready to test

Ubuntu SDK IDE

After a long development process, the new version of Ubuntu SDK IDE in beta version. We will be able to test this version, which comes packed with a new builder and execution engine to put aside all the old errors from past editions, and thus create our applications for Ubuntu Touch in a much faster and more intuitive way.

Some rumors pointed, and it is confirmed that they were right, that the new builders would be based on LXD containers that would replace the Scrap existing. After some time in reviewing and debugging the code, it is time to put it in the hands of the users and finish debugging this IDE.

The SDKs (Source Development Kit), and specifically the Ubuntu SDK, is a great application development environment that integrates a large number of resources, such as programs, libraries, code files, resources, etc. In short, everything you need to create a program that can work in the Ubuntu Touch systems. Thanks to this IDE, the management of resources can be done graphically and easily, as well as programming the code, debugging applications or reviewing documentation.

This new version aims correct problems slowness, mount point failures, and library errors encryptfs among others. In addition, among the new important changes we must mention that the support of applications that run from the host (The execution can be carried out, but the configuration file must be created manually), now it is necessary to create a container with the specific architecture of the device where we are going to execute the application.

Finally, in this version, constructors based on chroot. Although the feature will remain in some later versions, it will be permanently removed in the future development of this IDE.

Ubuntu SDK IDE installation

Installation is as simple as add the PPA repositories From the Ubuntu SDK tools run the aggregation of the packages:

sudo add-apt-repository ppa:ubuntu-sdk-team/tools-development 
sudo apt update && sudo apt install ubuntu-sdk-ide 

When it's over, we'll be done. The IDE must be fully functional and able to discover the containers as it was already the case with chroot. From a developer point of view, the experience shouldn't be much different than it was. However, do not stop being aware that we are facing a beta version that is not free of the odd one bugs,. If you find any you can report it via email, IRC or the project launchpad.

To start the IDE, enter the following command:

$ tar zcvf ~/Qtproject.tar.gz ~/.config/QtProject

The Ubuntu SDK IDE icon will appear in the Dash from where you can start it.

sdk-start-ide-from-dash

Typical problems and solution

Membership of the LXD group

Normally, the necessary groups are configured in the LXD installation for the correct execution of the environment. If for some reason this is not carried out satisfactorily, you can make sure that you belong to it by means of the following command:

sudo useradd -G lxd `whoami`

Then go back to log in in the system so that the group permissions take effect on your user.

Reset QtCreator settings

Sometimes QtCreator settings get corrupted and we must revert to a previous version for it to work. If this happens or you see Ghost Kits, there may be misconfigured devices. In general, it is possible to solve this situation by pressing the reset button within the QtCreator help or through the following command:

$ rm ~/.config/QtProject/qtcreator ~/.config/QtProject/QtC*

Delete old entries from schroots

As we already indicated, schroots it will be discontinued as of this version of the IDE. Even so, it will still remain in the system for a while and therefore it may be interesting to clean the click what we have done:

$ sudo click chroot -a armhf -f ubuntu-sdk-15.04 destroy
$ sudo click chroot -a i386 -f ubuntu-sdk-15.04 destroy

With this command we can free about 1.4 GB of disk space. Chroot clicks are hosted within the directory / var / lib / schroot / chroots /, so it may be a good idea to check that this folder is empty and there is nothing mounted in it. Do it through this command:

$ mount|grep schroot 

NVIDIA Driver Problems

Deploying applications locally from an LXD container cannot be carried out if our host uses NVIDIA card graphics drivers. If your graphics card has at least a dual processor, a little trick is to use the other processor that is not being used.

First of all, verify that you have a backup of your video card:

[php]$ sudo lshw -class display[/php]

If entries from another graphics card in the system, apart from NVIDIA itself, activate the other card and select it as primary:

 

$ sudo prime-select intel

 This utility may not be compatible with all systems and will certainly not work with bumblebee.

If your host only has a single NVIDIA graphics card, they may work for you the Nouveau drivers. Try them, maybe they will work for you. After all, this is one of the major glitches Canonical folks are working on right now.


The content of the article adheres to our principles of editorial ethics. To report an error click here.

Be the first to comment

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.