Ubuntu IDE breaks QtCreator dependencies mechanism

[Максим Савенков]

If I create a "C++ Library" project in Ubuntu IDE (or import a library-only project) and add it to my session, it is impossible to make it work as a dependency for other projects inside a session, because Ubuntu IDE will try to run deployment step after build library, which will fail. There is two possible failure reasons here:

1) If project (either CMake or QMake based) does not contain INSTALL directives (for example, if I have it set up in such way that I don't need them), the error will be about "make install" not found
2) If project does contain INSTALL directives, the error will be about "manifest.json not found"

If I create non-Ubuntu plain C library and app, there are no such errors, because there is no deployment step.

I'm not sure what Ubuntu IDE should do here, because it's not clear where libraries should be deployed, and if they are not deployed, the app that depends on them probably won't build, or won't run on device (especially in case of shared library dependency), but maybe this should be left for user do decided. At the very least, I think it is necessary to disable deployment step for projects that do not contain executables.

[Benjamin Zeller (zeller-benjamin)]

I'll need to check how I can workaround that problem. Since you can not depend on any external libraries with click packages most people use a subproject to build the libraries they need. So your setup is rather unusual in the click world.

However as a workaround for the time being you can remove the deploy steps from your library project in the project run configuration.

Currently a deploy config is created by default when a ubuntu device is set as a project target. Only thing I maybe can do is that to only create a runconfig when there is a manifest file specified. But I'll need to check first if that does not break other setups.

[Максим Савенков (max-savenkov)]

Actually, I'm not going to use this setup much either. It's just that someone may, and things will break for him without explanation. Maybe there is a way to mark Ubuntu-projects as "un-dependable", so they will not appear in dependencies dialog, or be greyed-out?