When icecc is not installed, the `which icecc` command in icecc-env.sh
returns nonzero. This happens when environment is being sourced. When
the terminal has `set -e`, the whole script fails and terminal is
closed.
Fix this by ignoring errors from the which command.
Signed-off-by: Adam Trhon
When icecc is not installed, the `which icecc` command in icecc-env.sh
returns nonzero. This happens when environment is being sourced. When
the terminal has `set -e`, the whole script fails and terminal is
closed.
Fix this by ignoring errors from the which command.
Signed-off-by: Adam Trhon
Finally we figured it out. When chaning EXTRA_OECMAKE with python
function, the function must not be registered like this:
addtask do_setup_extra_oecmake after do_patch before do_configure
but like this:
do_configure[prefuncs] += "do_setup_extra_oecmake"
I assume that as bitbake controls build
On Fri, 23 Jun 2017 13:53:05 +0100
"Burton, Ross" wrote:
> On 23 June 2017 at 11:57, Adam Trhon wrote:
>
> > According to documentation, this is expanded during recipe parsing. At
> > that time ${S}/oe_arguments.txt does not yet exits (it exists only after
> &
On Thu, 22 Jun 2017 22:51:26 +0100
"Burton, Ross" wrote:
> On 22 June 2017 at 09:42, Adam Trhon wrote:
>
> > but I am not very happy about using PACKAGECONFIG_CONFARGS - it feels
> > hacky, the
> > arguments are not shown in cmake fail log and it cann
I have a recipe that is configured by cmake. The cmake arguments are hardcoded
in the recipe and set using the EXTRA_OECMAKE variable. For various reasons, I
would like to have the arguments in a file in the project's upstream repository
(it's mine as well) and load them.
I came up with this:
do
