Building a click for a QML App with C++ plugin or QtQuick App with QML UI presents invalid options

Bug #1491708 reported by Didier Roche-Tolomelli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qtcreator-plugin-ubuntu (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When my projects contains some C++ code (classic case is one of the 2 previous options), building a click package presents you with 2 choices:
- Project with binary executables and libraries
- Project without binary executables and libraries (pure qml/html projects).

The second option can never work for those kinds of projects. I suggest that we scan the project qmake/cmake file and see from that which kind of project was selected.

Of course, there is always the chance for someone to select this kind of project, have the qmake/cmake template in it and deleting the backend/ directory, but I guess this will cover it.

Maybe a similar heuristic can be applied the other way as well.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: qtcreator-plugin-ubuntu 3.5.0+15.10.20150817-0ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 3 09:01:12 2015
InstallationDate: Installed on 2012-05-28 (1192 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: qtcreator-plugin-ubuntu
UpgradeStatus: Upgraded to wily on 2014-10-31 (306 days ago)

Tags: devexp
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :
Revision history for this message
Benjamin Zeller (zeller-benjamin) wrote :

What is currently happening is that we scan the project if it creates binaries and if it does preselect the correct option.

However there is no way of knowing if a project might copy binary files from the chroot and includes them into the package in the end, even if it does not create those itself. Which means it still needs to build against every chroot.

I remember there were some people doing that, installing extra packages on the chroots and then copying the libs
into the right folders.

So if I do not show that option people who need that feature can not fat package their project. But maybe we could make it more clear that most likely the selected option is valid?

Changed in qtcreator-plugin-ubuntu (Ubuntu):
status: New → Incomplete
Revision history for this message
Benjamin Zeller (zeller-benjamin) wrote :

We can however disable the option for the projects that create binaries .... what about the other option?

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

I guess disabling the optoin for the projects that creates binaries is a good first step. At least, we don't leave a broken option in that case, the other way is more "overkill" (like, doing stuff that's not needed), but "meh" ;)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qtcreator-plugin-ubuntu (Ubuntu) because there has been no activity for 60 days.]

Changed in qtcreator-plugin-ubuntu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.