<kayterina[m]>
Hello, a git repo that builds locally with autotools should it be made into a yocto recipe using "inherit autotools" or "inherit cmake"?
amitk has joined #yocto
gsalazar has joined #yocto
vladest has quit [Remote host closed the connection]
ptsneves has joined #yocto
<LetoThe2nd>
kayterina[m]: if it builds with autotools, it sounds very much like "inherit autotools", don't you agree?
<kayterina[m]>
Sure. It is this chapter in the manual that I am confused: "5.21.3 Building an Autotooled Package", it says: "Applications built with the Autotools such as autoconf and automake require a recipe that has a source archive listed in SRC_URI"
<kayterina[m]>
if the recipe builds in "git/" directory and has an empty build/, that is a case of autotools-brokensep?
zpfvo has quit [Ping timeout: 268 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
zpfvo has joined #yocto
<LetoThe2nd>
kayterina[m]: no, it is a case of setting S. look into any recipe that uses git, usually S = ${WORKDIR}/git
rfuentess has quit [Remote host closed the connection]
vladest has joined #yocto
bps3 has joined #yocto
bps2 has joined #yocto
florian has joined #yocto
bps3 has quit [Ping timeout: 240 seconds]
kpo has quit [Ping timeout: 248 seconds]
florian_kc has joined #yocto
PobodysNerfect has quit [Quit: Gone to sleep. ZZZzzz…]
PobodysNerfect has joined #yocto
<__ad>
is it possible to use eudev in place of systemd-udevd in kirkstone ?
<__ad>
i am getting an error adding eudev
<rburton>
yes, assuming you've turned off systemd. hard to help without knowing what the error is.
<__ad>
eudev was skipped: conflicting distro feature 'systemd' (in DISTRO_FEATURES)
<__ad>
so i should remove whole systemd ? eudev seems to be os independent
<rburton>
if you want to use eudev then by definition you don't want systemd
<rburton>
considering eudev is a fork of the udev in systemd
Guest46 has quit [Quit: Client closed]
<__ad>
uhm, is udev only a part of systemd ? can't be disabled just systemd-udevd ?
<rburton>
if you don't want systemd then remove it from your DISTRO_FEATURES (its not on by default, so you added it) and then you get eudev
<__ad>
mm ok. So eudev is a "whole" systemd replacement ?
<mcfrisk>
__ad: no it's not, but it conflicts with systemd which requires normal udev.
<rburton>
if you want a udev-like tool then your choices are eudev (traditional init) or systemd-udev (systemd). asking for systemd init with eudev isn't sensible.
<__ad>
mcfrisk: rburton: ok clear, thanks
<kayterina[m]>
How do I choose to make a recipe from a .tar.gz over the git repo? Does the repo suggests frequent changes?
<__ad>
(seen now requirements asks fir sysvinit, so good :)
<rburton>
kayterina[m]: official tarballs are smaller and easier to mirror so i tend to prefer those
<RP>
JPEW: I found that linux-yocto-rt issue. It was a bad recipe (v86d)
seninha has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
embetrix has joined #yocto
<embetrix>
Hello, I have defined the following bitbake variable:
<kayterina[m]>
is there an example of a recipe using multiple licenses? there are 3 license files in the repository and the source code itself has some files under apache2.0,some BSD-2, some BSD-3
<kayterina[m]>
*not license files, there is a COPYING, a LICENSE and a copyright in the repo
<mcfrisk>
is bitbake-diffsigs usable to anyone? It's "NOTE: Starting bitbake server..." for ever on my trivial master branch setup..
<qschulz>
kayterina[m]: you can have multiple entries in LIC_FILES_CHKSUM if that is your question/
<qschulz>
You can have binary operators in the LICENSE field too
<rburton>
kayterina[m]: many in core. just list them all in LICENSE in the appropriate form (is it apache *or* bsd, or apache *and*), then list them all in the checksum and ideally some summary of what files are what license (like a readme fragment that explains the licensing)
<embetrix>
it works I think only when using python, I would like to use it like this :
<rburton>
write a little function to do the parsing for you and call that instead of d.getVarFlag
tgamblin has joined #yocto
<embetrix>
"${@d.getVarFlag('TF_A_CONFIG', d.getVarFlag('config'))}" is not working
<rburton>
you meant d.getVar() for the second one
<rburton>
at least i guess
<rburton>
d.getVar("FOO") gets the value the variable. if FOO="bar", returns 'bar'
<rburton>
d.getVarFlag(name, flag) returns the value of the named flag. FOO[fish]="dog" and d.getVarFlag("FOO", "fish") returns "dog"
<embetrix>
yes sorry you are right I got them mixed up
<embetrix>
but what is the right way to use it : ${@d.getVarFlag("TF_A_CONFIG", d.getVar("config"))} and "${@d.getVarFlag("TF_A_CONFIG", ${@d.getVar("config")})}" are not working
<rburton>
what is this 'config' varable you refer to
<rburton>
oh you don't need the ${@} inside
<rburton>
${@ ... } is expand-this-python
<rburton>
once you're inside you don't need to ${@} again
<kayterina[m]>
rburton: the readme-like fragment that lists the files and their licenses is inside the repo (unibuild-packaging/deb/copyright). Is listing this file and its checksum enough?
<rburton>
embetrix: oh i see your example above. expanded python at parse time for obvious reasons doesn't have access to bash variables at runtime.
<rburton>
${@} expansion happens when the shell script is *written out* so it can't see bash variables
<amsobr>
Hey all. I'm building a nodejs project using bitbake. Thing is, some of the dependencies needed for the build are actually listed in "devDependencies" and it seems that even if I provide a shrinkwrap file generated with NODE_ENV=development, only the "depends" turn out to be populated in node_modules when I attempt to build the package.
<amsobr>
So while I can patch the packages.json to work around that, I'm wondering is there's any OE trick I can use to also pull the "devDepends" os package.json into the work area...
<amsobr>
err, "devDependencies", I mean... :)
<rburton>
maybe the tool should pull in those deps for the build
<vvn>
Do I recall correctly what we have a phytec dev in this channel? :)
<amsobr>
humm, not sure if I follow. The way I tried is to set NODE_ENV=development, run npm install and get the shrinkwrap, under a container with the same node version as OE (node:16)
<vvn>
s/what/that/
<amsobr>
I can see that the shrinkwrap contains the needed libs, under "devDependencies" as well so I assume this might be why they don't end up populated when building under bitbake.
<amsobr>
running devshell and checking node_modules it turns out that the devDependencies aren't present.
<amsobr>
Anyway, no big deal, it's workable with a patch on packages.json
bps2 has quit [Ping timeout: 250 seconds]
beroset has joined #yocto
<beroset>
For the SRCREV variable, the description says "Note that if you want to build a fixed revision and you want to avoid performing a query on the remote repository every time BitBake parses your recipe, you should specify a SRCREV that is a full revision identifier and not just a tag."
<beroset>
I know what a tag is in the context of git, but what is a "full revision identifier"?
<rburton>
beroset: a SHA
<beroset>
Does that mean a specific git hash or something else?
<rburton>
yes, a full hash
<beroset>
OK, thanks for the confirmation.
<beroset>
Maybe an example there might be useful? Or perhaps a link to a definition for "full revision identifier"?
<rburton>
changing it to use the git terminology of "sha1 object name" seems sensible. fancy sending a quick patch
<rburton>
?
AdrianTheFirst has quit [Ping timeout: 245 seconds]
<beroset>
That would cover the case for git. I don't know about current versions of subversion, mercurial and bazaar.
goliath has joined #yocto
<beroset>
I'm thinking perhaps a parenthetical like this: "a full revision identifier (e.g. the full SHA hash in git) and not just a tag."
<rburton>
sounds good
beroset has quit [Quit: Client closed]
beroset has joined #yocto
<mason>
smooge: o/
leon-anavi has quit [Quit: Leaving]
seninha has quit [Ping timeout: 256 seconds]
<beroset>
OK, if I did everything correctly, there should be a patch in the email list.
beroset has quit [Quit: Client closed]
pabigot has quit [Remote host closed the connection]
beroset has joined #yocto
pabigot has joined #yocto
frieder has quit [Remote host closed the connection]
zpfvo has quit [Ping timeout: 256 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
ptsneves has quit [Ping timeout: 256 seconds]
dgriego has joined #yocto
kscherer has quit [Quit: Konversation terminated!]
kscherer has joined #yocto
florian_kc has joined #yocto
gsalazar has quit [Ping timeout: 268 seconds]
bluelightning has quit [Ping timeout: 256 seconds]
bluelightning has joined #yocto
florian_kc has quit [Ping timeout: 246 seconds]
prabhakarlad has quit [Quit: Client closed]
jonmason has quit [Read error: Connection reset by peer]
jonmason has joined #yocto
awafaa has quit [Read error: Connection reset by peer]
shoragan has quit [Remote host closed the connection]
awafaa has joined #yocto
Colin_Finck has quit [Quit: No Ping reply in 180 seconds.]
shoragan has joined #yocto
Colin_Finck has joined #yocto
amitk has joined #yocto
florian_kc has joined #yocto
yannd has quit [Ping timeout: 240 seconds]
yannd has joined #yocto
goliath has quit [Quit: SIGSEGV]
mrnuke has quit [Ping timeout: 240 seconds]
mrnuke_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
otavio_ has quit [Quit: Lost terminal]
otavio has joined #yocto
seninha has joined #yocto
seninha has quit [Remote host closed the connection]
seninha has joined #yocto
rfs613 has quit [Ping timeout: 256 seconds]
Minvera has quit [Remote host closed the connection]
Minvera has joined #yocto
rfs613 has joined #yocto
LocutusOfBorg has quit [Ping timeout: 250 seconds]
LocutusOfBorg has joined #yocto
amitk has quit [Ping timeout: 250 seconds]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
alessioigor has quit [Quit: alessioigor]
kpo has quit [Ping timeout: 240 seconds]
tgamblin has quit [Ping timeout: 240 seconds]
prabhakarlad has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Thorn has quit [Ping timeout: 240 seconds]
kscherer has quit [Quit: Konversation terminated!]