**** BEGIN LOGGING AT Sat Jul 16 02:59:58 2016
Jul 16 09:56:30 <willeponken> hi, where are kernel parameters defined?
Jul 16 15:50:00 <sveinse> How can I set an environment variable to a command? In this case to qmake. Please note that EXTRA_QMAKE_VARS give parameters /to/ qmake, not as env vars, e.g. "qmake VAR=12", which is interpreted internally differently than "VAR=12 qmake"
Jul 16 15:56:46 <sveinse> Answer to self: OE_QMAKE_QMAKE_prepend="VAR=12 "
Jul 16 19:17:54 <rburton> sveinse: or export in the recipe
Jul 16 19:18:13 <rburton> (OE_QMAKE_QMAKE_prepend is a hack solution)
Jul 16 19:32:16 <sveinse> rburton, all right, thanks
Jul 16 19:33:23 <rburton> export FOO="bar" in the recipe will export the variable to all tasks that run
Jul 16 19:34:39 <sveinse> rburton, that also defines ${FOO} for use within the recipe also, right?
Jul 16 19:34:44 <rburton> yes
Jul 16 19:34:57 <rburton> creates a variable that is also exported into shell-land
Jul 16 20:23:56 <sveinse> Does bb/oe have some mechanism for build version management? Like increasing build numbers?
Jul 16 20:31:29 <sveinse> rburton: seems the OE_QMAKE_QMAKE_prepend hack might be compulsory. The env var qmake needs is TARGET_PREFIX. Not one that bb is happy with being used in the recipe apparently :(
Jul 16 21:19:15 <rburton> sveinse: if you enable the PR service then PR (package revision) will incrememnt on every build for you
Jul 16 23:10:10 <sveinse> Where in the source is do_compile() for makefile defines? grep gives me loads...
Jul 16 23:11:07 <sveinse> I'd like to look at it, as I'd want to run compilation through a output styler that we use "qstyler -o logfile -- make ..."
Jul 17 00:23:42 <sveinse> I found it in meta/classes/base.bbclass, oe_runmake_call(). And once more _prepend comes to the rescue.
Jul 17 00:24:47 <sveinse> Why is doing MAKE_prepend="myfilter " and such frowned upon and considered a hack? I does exactly what I want it to
**** ENDING LOGGING AT Sun Jul 17 02:59:58 2016