On Mon, 05 Dec 2016 21:06:05 Paulo Neves wrote:
> Hello Paul, I understood that. The part of the specific paths is the
> one that breaks convention and has no easily visible documentation, or
> am I missing something.
We do mention it in at least a couple of places:
On Mon, 05 Dec 2016 09:42:42 Nicolas Dechesne wrote:
> On Mon, Dec 5, 2016 at 7:59 AM, Paulo Neves wrote:
> > I have a recipe which depends on another package's file to do it's
> > job. How can I arbitrarily access a file from another package which my
> > recipe depends on?
>
On Mon, Dec 5, 2016 at 7:08 AM, Paulo Neves wrote:
> Hello Nicolas, thank you for your advice and hints but I "need" to
> corrupt a bit the conventions of yocto and use specific package names
> (due to compatibility with other older build systems)
>
> The magic behind the fact
Hello Nicolas, thank you for your advice and hints but I "need" to
corrupt a bit the conventions of yocto and use specific package names
(due to compatibility with other older build systems)
The magic behind the fact that my special package sysroot directories
were not being moved to the yocto
On Mon, Dec 5, 2016 at 10:10 AM, Paulo Neves wrote:
> Sorry for my ambiguity. When I mentioned binaries I meant general
> binary data, not necessarily executable. Their only need is that the
> new recipe needs to be fed these data from the other package so it can
> produce
Sorry for my ambiguity. When I mentioned binaries I meant general
binary data, not necessarily executable. Their only need is that the
new recipe needs to be fed these data from the other package so it can
produce it's own output. This binary data only needs to be available
in the host pc, in the
On Mon, Dec 5, 2016 at 9:54 AM, Paulo Neves wrote:
> The files form this other package are mostly binaries in a directory
> structure. I have to create an additional package which works with the
> other package's(the dependency) installed directory structure.
> Also you hinted
Hi Nicolas,
The files form this other package are mostly binaries in a directory
structure. I have to create an additional package which works with the
other package's(the dependency) installed directory structure.
Also you hinted at something I didn't know before, which was that
packages need to
On Mon, Dec 5, 2016 at 7:59 AM, Paulo Neves wrote:
> I have a recipe which depends on another package's file to do it's
> job. How can I arbitrarily access a file from another package which my
> recipe depends on?
>
> I searched for this kind of problem but did not find it
Hello,
I have a recipe which depends on another package's file to do it's
job. How can I arbitrarily access a file from another package which my
recipe depends on?
I searched for this kind of problem but did not find it
Best regards
Paulo Neves
--
10 matches
Mail list logo