After a long process of development, the new version of the Ubuntu IDE SDK in beta. We will be able to test this version, which comes packaged with a new builder and runtime engine to put aside all the old errors of 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 schroot existing. After some time in code review and debugging, it’s time to put it in the hands of 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 lot of resources, Such as programs, libraries, code files, resources, and so on. In short, everything you need to be able to create a program and make it work in the Ubuntu Touch systems. Thanks to this IDE, we can manage resources graphically and easily, as well as programming the code, debugging applications or reviewing documentation.
This new version aims correct problems of slowness, of assembly point failures, and errors with the library encryptfs others. In addition, important new changes include the removal of support for applications running from host (The execution can be carried out, but the configuration file must be created manually), being necessary now to create a container with the specific architecture of the device where we are going to run the application.
Finally, in this version the constructors based on will stop being able to be used chroot. Although the feature will remain in some later versions, it will be permanently removed in the future development of this IDE.
Installing the Ubuntu IDE SDK
Installation is as simple as add PPA repositories of the Ubuntu SDK tools run package aggregation:
sudo add-apt-repository ppa:ubuntu-sdk-team/tools-development sudo apt update && sudo apt install ubuntu-sdk-ide
When it is over we will be done. The IDE must be fully functional and able to discover the containers as it already happened with chroots. From a developer point of view the experience should not be very different from how it was. However, be aware that we are facing a beta version that is not free of the occasional error. If you find any you can report 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.
Typical problems and solution
Membership in the LXD group
normally in the LXD installation the necessary groups are configured for the correct execution of the environment. If for some reason this is not done satisfactorily, you can make sure that you belong to it by the following command:
sudo useradd -G lxd `whoami`
Then go back to loggearos in the system for group permissions to take effect on your user.
Reset QtCreator settings
sometimes QtCreator settings are corrupted and we need to 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 resolve this situation by pressing the reset button within the QtCreator help or by using the following command:
$ rm ~/.config/QtProject/qtcreator ~/.config/QtProject/QtC*
Delete old schroots entries
As we already told you, schroots will be abandoned from this version of the IDE. Even so, owning one is still beyond the reach of the average person it can be interesting to clean them 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 will be able to release around 1.4 GB of disk space. Chroots clicks are hosted within directory / Var / lib / schroot / chroots /, So it may be a good idea to check that this folder is empty and there is nothing mounted on it. Do it through this command:
$ mount|grep schroot
Problems with the NVIDIA driver
Deploying applications locally from an LXD container cannot be carried out if ours host uses NVIDIA graphics card 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, make sure you have a backup of your video card:
php]$ sudo lshw -class display[/php]
If entries are displayed 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 main system has only one NVIDIA graphics card, it may work for you Nouveau drivers. Try it, because maybe they work for you. After all, this is one of the main mistakes the people at Canonical are working on right now.