Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Support building all project in one directory
Date: Fri, 15 Jan 2010 09:23:50 +0100	[thread overview]
Message-ID: <hip8ml$2mq$2@ger.gmane.org> (raw)
In-Reply-To: <201001150733.59792.marcin@juszkiewicz.com.pl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15-01-10 07:33, Marcin Juszkiewicz wrote:
> Dnia piątek, 15 stycznia 2010 o 02:35:13 Guo Hongruan napisał(a):
>> 在 Fri, 15 Jan 2010 03:53:01 +0800,Khem Raj <raj.khem@gmail.com> 写道:
>>> On (14/01/10 17:19), Guo Hongruan wrote:
>>>> After changing this way, the native tools can be shared with
>>>> different buildings.
>>>
>>> They get shared even now. I have my TMPDIR = /scratch/oe/build and
>>> DEPLOY_DIR = ${TMPDIR}/deploy/${LIBC}
>>>
>>> I share the native tools all the time
>  
>> This way, the packages built in ${TMPDIR}/work/ will bother each other. It
>> is obvious that a binary package built based on uclibc is different with
>> the same one built base on glibc. So I think it's better to classify them
>> using ${LIBC}.
> 
> As long as you do build for uclibc and glibc/eglibc in one TMPDIR they are 
> fine due to different TARGET_SYS. Problem starts when you want to share glibc 
> and eglibc builds as they use same TARGET_SYS. And thats when you need 
> something to separate TMPDIR. But as I wrote before you can alter name of 
> directories in your local.conf without changing them for rest of our users.

Or you can just use angstrom, which has all that magic already :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLUCYWMkyGM64RGpERAlzFAKCMEP4Gvm64Jr6LU28MamhAmdlULACcCKrK
xja2GfGxhQs2avrMe/3CZIw=
=vIXP
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-01-15  8:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  7:55 [PATCH] Support building all project in one directory Guo Hongruan
2010-01-14  9:14 ` Marcin Juszkiewicz
2010-01-14  9:19   ` Guo Hongruan
2010-01-14 19:53     ` Khem Raj
2010-01-15  1:35       ` Guo Hongruan
2010-01-15  3:47         ` Mike Westerhof
2010-01-15  9:17           ` Guo Hongruan
2010-01-15  9:56             ` Phil Blundell
2010-01-15 10:42               ` Guo Hongruan
2010-01-15 10:46                 ` Phil Blundell
2010-01-15 10:59                   ` Guo Hongruan
2010-01-15 12:50                     ` Phil Blundell
2010-01-15 12:57                       ` Guo Hongruan
2010-01-15 13:02                         ` Phil Blundell
2010-01-15 13:09                           ` Guo Hongruan
2010-01-15 11:00                 ` Koen Kooi
2010-01-15 10:43               ` Guo Hongruan
2010-01-15  6:33         ` Marcin Juszkiewicz
2010-01-15  8:23           ` Koen Kooi [this message]
2010-01-15  9:23             ` Guo Hongruan

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='hip8ml$2mq$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox