LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
alessioigor has quit [Ping timeout: 256 seconds]
mulk has quit [Ping timeout: 272 seconds]
mulk has joined #yocto
<simonew> yocton: Agreed, I thought this was the time waited in the past though. NVD answered me today as well for a mail from last sunday. Not sure how they handle it. We could wait a month? Then we could basically allign it more or less with the Mx milestones.
yudjinn has quit [Ping timeout: 252 seconds]
Vonter has quit [Ping timeout: 252 seconds]
mulk has quit [Ping timeout: 255 seconds]
Vonter has joined #yocto
mulk has joined #yocto
lexano has quit [Ping timeout: 256 seconds]
yudjinn has joined #yocto
paulg has joined #yocto
rm5248 has quit [Quit: Leaving.]
nerdboy has quit [Ping timeout: 256 seconds]
Vonter has quit [Ping timeout: 260 seconds]
nerdboy has joined #yocto
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #yocto
luc4 has quit [Quit: Konversation terminated!]
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
hays has quit []
dgriego has quit [Ping timeout: 246 seconds]
dgriego has joined #yocto
mattsm has quit [Quit: Ping timeout (120 seconds)]
mattsm has joined #yocto
Thorn has joined #yocto
Thorn_ has quit [Ping timeout: 256 seconds]
xmn has quit [Ping timeout: 272 seconds]
Chaser has joined #yocto
alessioigor has joined #yocto
Chaser has quit [Client Quit]
dkc has quit [Read error: Connection reset by peer]
dkc has joined #yocto
Chaser has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mattsm1 has joined #yocto
mattsm has quit [Ping timeout: 255 seconds]
mattsm1 is now known as mattsm
florian_kc has joined #yocto
Chaser has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
Kubu_work has joined #yocto
goliath has joined #yocto
zkrx has quit []
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mischief has quit [Read error: Connection reset by peer]
jmd has joined #yocto
mulk has quit [Ping timeout: 268 seconds]
mulk has joined #yocto
zkrx has joined #yocto
zkrx has quit [Ping timeout: 252 seconds]
lexano has joined #yocto
mckoan|away has quit [Ping timeout: 246 seconds]
mckoan|away has joined #yocto
xmn has joined #yocto
Chaser has joined #yocto
Guest36 has joined #yocto
<Guest36> vizarsky: hello could someone help me do debug the case? The case is next: I have 2 recipes: foo and bar. foo is set of c++ my custom libraries. Foo target is build successfully. While building bar - which is binaries which links on set of libraries from foo I see that libraries from foo populated in sysroot - everything OK. Configuration stage of
<Guest36> bar cmake shows all of depencies - all include directories and linkage are OK. But... during compilation of bar headers from foo are absent in compile cmd.
<Guest36> vizarsky: compilation of bar failed due absent includes in compile command... Though all header are in place... bar CMakeLists.txt explicity includes foo dependecies via target_link_libraries call. Bar recipe has runtime and buildtime depencies on foo. So, I don't understand what is wrong in my enviorment.
<Guest36> I set up cmake packages via cmake files which are products of foo recipe
<Guest36> during bar configuration I call find packages in cmkae files and see that cmake packages of foo were found with correct includes and libraries
<Guest36> but compilation log does not show even that bar links or inlcudes somethings from foo.
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mulk has quit [Ping timeout: 260 seconds]
mulk has joined #yocto
<Guest36> I understand that a lot of undefined variables in my messages :)
Vonter has joined #yocto
ptsneves has joined #yocto
ptsneves has quit [Ping timeout: 272 seconds]
zkrx has joined #yocto
ptsneves has joined #yocto
ptsneves has quit [Ping timeout: 268 seconds]
ptsneves has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
goliath has quit [Quit: SIGSEGV]
mulk has quit [Ping timeout: 272 seconds]
mulk has joined #yocto
Guest36 has quit [Quit: Client closed]
amitk has quit [Ping timeout: 268 seconds]
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 255 seconds]
Guest36 has joined #yocto
Guest36 has quit [Ping timeout: 250 seconds]
Chaser has joined #yocto
vladest has quit [Remote host closed the connection]
Chaser has quit [Ping timeout: 252 seconds]
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
pbsds has joined #yocto
vladest has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
jmd has quit [Remote host closed the connection]
Guest18 has quit [Quit: Client closed]
<jclsn> Could I use Yocto to build statically linked binaries for a machine?
<jclsn> I have an armv7l board that I can't flash anything new to, else I would brick it. I can also not install libraries into the rootfs. So the only way is having statically linked binaries. It is tedious to build those manually. I would somehow have to set up a generic armv7 target and make builds static by default
<jclsn> Not sure if buildroot would be the better choice here
<Crofton> jclsn: it should be possible
<Crofton> how many binaries do you need to build static?
<jclsn> Crofton: No idea. I want to be able to build whatever I want, without having to search for sources etc
<Crofton> I ahve seen people create toolchains with static versions of the libs, so they can build things adn drop them into random file systems before
<jclsn> Sure it is possible
<jclsn> I just have never used Yocto that way
<jclsn> Usually you build and image and flash that
<Crofton> Right
<Crofton> People do all manner of things
<Crofton> Basically right a recipe to build something and chose options to statically link it
<Crofton> I forget if you need to set a "feature" to get static libs creaeted wherever possible
<jclsn> Seems like Yocto is overkill for this
<jclsn> Too many knobs to turn
<RP> Can be done but we do disable static libs by default. That much is easy to change by dropping the appropriate meta/conf/distro/include file
<Crofton> I thought that might be the case ...
Kubu_work has quit [Quit: Leaving.]
<Crofton> If you ahve a complex depends chain, you will eventually come back to the yocto project though
<jclsn> RP: What is this file that you are talking about? Can't I just set a global CFLAGS="${TARGET_CFLAGS} -static" ?
<jclsn> in local.conf
<RP> meta/conf/distro/include/no-static-libs.inc
<RP> as long as that isn't included it should build shared and static libs
<RP> then you just need to convince it to static link the binaries
<jclsn> So just delete the file?
<jclsn> Ah I can probable doe an EXTRA_OECONF:remove = "${DISABLE_STATIC}"
<jclsn> Seems to work. It is reconfiguring everything
<jclsn> Now I just need to set a proper machine
<jclsn> Not sure if qemuarm will suffice for armv7l
<Crofton> not all packages like to build static libs and static binaries
<jclsn> Crofton: meaning?
<jclsn> Some will fail with the -static flag?
<Crofton> I think so
<jclsn> Then I need an easy way to set the flag for a list of images
<jclsn> s/images/packages/
<jclsn> Doing a .bbappend for every package I want to build is not practical
<Crofton> try what RP suggested
<jclsn> Already did that
<jclsn> Added a EXTRA_OECONF:remove = "--disable-static" to local.conf
<jclsn> But that is a global setting
<jclsn> My bitbake recipe skills are lagging here I guess. You can probably make this setting only for a list of packages
<jclsn> For now nothing has failed thouhg
<jclsn> Even glibc compiled. No idea how that could be static ^^
<jclsn> The setting probably didn't achieve what I am intending
<jclsn> Ah there, it failed ^^
mulk has quit [Ping timeout: 255 seconds]
<rburton> jclsn: no-static-libs is a *poky* thing. you should make your own distro and not include that file. that's how its meant to be done.
mulk has joined #yocto
<rburton> poky is a *reference and example* distro for *our testing purposes*
<jclsn> Have never done that from scratch
<jclsn> and I am not sure if that is worth the trouble for some toy project
<jclsn> I just want to build some statically linked binaries
<rburton> set DISABLE_STATIC="" in your local.conf but making a 'new' distro is about four lines of code
<rburton> that will disable the no-static include and it will build static libs for everything
<jclsn> I just need it for certain packages though
<rburton> then set that in the recipe or bbappends or use overrides in local.conf
<rburton> you said that setting it per-recipe was too much effort, so i was giving you a one-shot for the entire distro
<jclsn> Okay okay
<rburton> there are many ways :)
<jclsn> So create a new layer and copy the disable-static.inc to conf/distro/includes?
<jclsn> Then set DISABLE_STATIC = "" in there?
<rburton> that would be the worst way
<jclsn> hmpf
<rburton> if you want to just build static libs globally, DISABLE_STATIC="" in your local.conf
<rburton> (as i said above)
<jclsn> You said creating a distro were better
<rburton> right, create a new distro.conf file and just don't include no-static-libs.inc
<rburton> including it is something poky.conf does. your distro .conf doesn't have to.
<jclsn> But inlcude everything else I guess?
<rburton> https://github.com/rossburton/customdistro/blob/master/meta-custom/conf/distro/custom.conf <-- behold the smallest distro conf i could think of
<jclsn> There are many things in meta/conf/distro/includes
<rburton> have an actual look at poky.conf and you'll see it doesn't actually do much. it mainly turns more stuff on.
rbox has joined #yocto
<rburton> stuff you might want want, like no-static-libs
<jclsn> Okay seems to work
<jclsn> Will qemuarm be enough for armv7?
<jclsn> I think there some differences between armv6 and armv7
<jclsn> than both being 32-bit systems
<rburton> are you aiming to run on a specific board?
<rburton> qemuarm pretends to be a cortex-a15, arm7a
<jclsn> It is for my LG webOS TV
<jclsn> Some guys rooted in and are creating Homebrew apps for it
<jclsn> Most TVs run armv8, but even LG seems to build armv7 binaries to make them compatible with every hardware
<rburton> you know webos is yocto already right :)
<jclsn> I know
<jclsn> But the bsp is not public
<rburton> just build a qemuarm SDK and use that if you're literally making apps
<jclsn> I also wouldn't dare to flash the TV with any image. It just cost too much :D
<jclsn> That is what I was trying
<rburton> you'll want to build the entire sdk with static libraries present (so definitely set DISABLE_STATIC globally) and iirc you'll want to add staticdev-pkgs to SDKIMAGE_FEATURES
<jclsn> Thanks
GNUmoon has joined #yocto
neofutur_ has quit [Ping timeout: 252 seconds]
nerdboy has quit [Read error: Connection reset by peer]
neofutur_ has joined #yocto
Lihis has quit [Quit: Quitting]
Lihis has joined #yocto
<rbox> i'm trying to figure out how to get opkg-utils removed from the image, it appears as that is the default provider for update-alternatives, i can't figure out how to disable update-alternatives
astlep55040180 has quit [Ping timeout: 252 seconds]
<rbox> it says it'll remove update-altneratives from a read only, but i dont want to compile it at all
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
Saur_Home has joined #yocto
astlep55040180 has joined #yocto
alessioigor has quit [Quit: alessioigor]
florian_kc has quit [Ping timeout: 252 seconds]