| 20:33.29 | *** join/#oe infobot (ibot@208.53.50.138) |
| 20:33.29 | *** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel |
| 20:40.59 | jeroen_ | kergoth: we will see, I guess I will hit in one or more issues anyway ;) |
| 20:49.52 | *** join/#oe contempt (contempt@unaffiliated/contempt) |
| 21:04.47 | *** join/#oe khem` (~khem@unaffiliated/khem) |
| 21:07.10 | jeroen_ | kergoth: ah now I understand what you meant I guess, the split of libc6.bb and libc6-dev.bb, that can be easily changed.. it is auto generated.... |
| 21:07.39 | kergoth | right, libc6 is virtuallibc, but libc6-dev is linux-libc-headers, etc |
| 21:08.00 | kergoth | but yeah, you could either change how they're generated, or just create empty wrapper recipes that depend on the pieces and set provides in that |
| 21:08.36 | kergoth | the assumption by the build is that once virtual/libc has been built, both the c library and its headers are available in the sysroot, of course |
| 21:29.31 | *** join/#oe jackmitch|home (~Thunderbi@cpc2-slam8-2-0-cust880.2-4.cable.virginm.net) |
| 21:31.11 | jeroen_ | kergoth: it works good enough for my hacking, see https://github.com/jhofstee/meta-bin-deb/commit/f3c057b83b910bfa6edc64d895208f67290ad848#diff-368a4a9359252ef559db6882f887a894R155 |
| 21:34.20 | *** join/#oe darkschneider (~gab@93-32-51-166.ip32.fastwebnet.it) |
| 22:01.01 | jeroen_ | kergoth: happen to know how to prevent a package being created in deploy/*? |