[oe] [meta-qt5] Do_install_append() with qmake
Dylan Bartlett
dylan.bartlett at metixmedical.co.uk
Fri May 25 17:10:38 UTC 2018
Sorry all, ignore this. Do_install_append works, from what I can only call
a formatting issue in my recipe seems to have stopped the _append from
running.
Fixing some of the formatting in my _append function seems to have started
things working.
My next issue seems to be that my application is building in a debug
configuration and the linker is producing a pretty large binary (~150MB).
But I haven't exhausted myself on that issue yet.
Thanks for taking the time to reply even though this is my own fault,
Dylan
On Fri, 25 May 2018 at 10:31 Dylan Bartlett <
dylan.bartlett at metixmedical.co.uk> wrote:
> Hello all,
>
> I hope you'll be able to help clear some things up for me.
>
> I have created a recipe to build and install a Qt Application I've been
> developing, so far everything has been working great and the program gets
> compiled, installed and packaged.
>
> However there is one additional install step I need to complete, which is
> creating a symbolic link to my binary in /opt to /usr/bin/b2qt. I want to
> do this so that the Boot2Qt appcontroller starts my application on boot.
>
> There are two ways I thought I could do this.
> 1. Use do_install_append() in the recipe to create the symbolic link.
> However qmake5.bbclass does not export the do_install function. Modifying
> the .bbclass with EXPORT_FUNCTIONS do_install breaks everything so I think
> that this is the wrong way to go about it.
>
> 2. Use target.extra in the qmake .pro file to add the extra commands.
> This one I had a bit more success with, I added my commands to
> target.extra and built the recipe.
> In this case do_install appeared to run properly. I could see my symbolic
> link in the image directory however the binary that was complied no longer
> appears in the image directory. So I've fixed one thing and broke another.
>
> At this point I've reached the end of what I think I can try, I'm sure I'm
> missing something simple since extra install steps are a common task. Can
> someone tell me what the canonically correct way that I should be doing
> this is?
>
> I've attached my recipe and a segment of my .pro if that helps.
>
> Best Regards,
> Dylan Bartlett
>
More information about the Openembedded-devel
mailing list