ubuntu-phone team mailing list archive

[Robert Schroll <rschroll@xxxxxxxxx>]

On Mon, Feb 2, 2015 at 3:15 AM, Benjamin Zeller 
<benjamin.zeller@xxxxxxxxxxxxx> wrote:
> Yes, thats required. QtCreator needs to find out which hooks will be 
> provided by the click package in the end. We can not just check the
> project files for binaries and use those as base for the runconfigs. 
> Not every binary may be represented by a hook and even if it is
> the hook can be named completely different. So the manifest.json 
> files are the only source we can use to figure out which 
> runconfigurations
> make sense.

I have no idea what's going on behind the scenes, so these may be 
stupid questions, but: Why can't you look for the manifest.json file 
that results from the build?  You know the filename, right?  There's 
the obvious problem that you can't figure out the run options until 
you've built it once, but that's a one-time problem.

Right now, I'm pointing Qt Creator to a manifest.json.in file, which 
has bits that will be filled in by cmake.  How much can I do at 
compile-time before I break Qt Creator integration?

> Its documented in the project templates, but it would be good to 
> document is some more I agree.

Frankly, documenting something that breaks existing projects in a place 
where it'll only be seen by new projects is completely useless.

Thanks for the explanations,
Robert