From: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: Question about package prefix
Date: Fri, 16 Dec 2011 23:35:37 +0100 [thread overview]
Message-ID: <1845722180277205462@unknownmsgid> (raw)
In-Reply-To: <CAMKF1srRe_ksYrw3Zq+ScS0ED12e7QoeGurtynybsFOvACH1-Q@mail.gmail.com>
I'm sorry but I'm not able to find the meta-micro file. I searched it
under meta directory without success (openembedded git repos).
Any suggestions?
Il giorno 16/dic/2011, alle ore 23:24, Khem Raj <raj.khem@gmail.com> ha scritto:
> On Fri, Dec 16, 2011 at 2:12 PM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
>> Thanks so much!!!
>> Do you mean I have to write a unified (in distro/machine conf dir)
>> do_install to be propagated to all the built packages?
>>
>> Regards,
>> Giuseppe
>>
>> Il giorno 16/dic/2011, alle ore 23:01, Khem Raj <raj.khem@gmail.com> ha scritto:
>>
>>> On (16/12/11 10:36), Giuseppe Condorelli wrote:
>>>> Hi All,
>>>>
>>>> I need to package against a different prefix using rpm. I mean, I don't
>>>> want to have to files located with
>>>> the absolute path (i.e. /usr/lib/ etc...) but I need to have them under a
>>>> specified path.
>>>> How can I obtain this? I saw conf/bitbake.conf contains many variable to be
>>>> accordingly set (prefix, exec_prefix, etc...)
>>>> but if I modify them the build will be broken. Also, looking at the
>>>> distro/<distros>.conf files I have not seen nothing similar.
>>>> Please can you suggest me something to solve my issue?
>
> hmm I thought you wanted to do it just for one package.
> do you want whole image to be relocated to this location.
> the see how micro does it look at meta-micro
>
>>>
>>> write do_install so they get installed in the new location.
>
>
>
>>>
>>>>
>>>> Thanks,
>>>> Giuseppe
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>> --
>>> -Khem
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-12-16 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 9:36 Question about package prefix Giuseppe Condorelli
2011-12-16 22:01 ` Khem Raj
2011-12-16 22:12 ` Giuseppe Condorelli
2011-12-16 22:23 ` Khem Raj
2011-12-16 22:35 ` Giuseppe Condorelli [this message]
2011-12-16 22:40 ` Paul Eggleton
2011-12-16 22:43 ` Giuseppe Condorelli
2011-12-20 13:42 ` Giuseppe Condorelli
2011-12-28 9:40 ` Giuseppe Condorelli
2011-12-28 10:10 ` Paul Eggleton
2011-12-28 15:40 ` Giuseppe Condorelli
2011-12-28 15:51 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1845722180277205462@unknownmsgid \
--to=giuseppe.condorelli@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.