Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: developmet setup
Date: Thu, 27 May 2010 13:16:07 -0400	[thread overview]
Message-ID: <20100527171607.GK23464@denix.org> (raw)
In-Reply-To: <201005271742.21771.vladimir.davydov@promwad.com>

On Thu, May 27, 2010 at 05:42:21PM +0300, Vladimir Davydov wrote:
> Hi,

Has anyone looked at srctree class from kergoth? There were some usage 
examples on the list before...


> Maybe following way will not usefull for you, but it is working for me.
> 
> I have overrided do_fetch() method in the kernel recipe to make symlink to my 
> kernel source tree, which is under git control.
> 
> S = "${WORKDIR}/linux-2.6"
> 
> do_fetch () {                                                                                                                                          
>   cd ${WORKDIR}                                                                                                                                      
>   if [ ! -L ${S} ]; then                                                                                                                             
>     ln -sf ${MY_KERNEL_PATH} ${S}                                                                                                             
>   fi                                                                                                                                                 
> }                                                                                                                                                      
> 
> MY_KERNEL_PATH is the local path to my kernel source tree. It is passed from  
> environment variables.
> I'm using this way only for kernel development.
> 
> 
> > Hi all,
> > I was searching a clean way to develop in OE my new kernel and my new
> > applications.
> > 
> > I saw this nice article about kernel development:
> > http://bec-systems.com/site/521/best-practices-for-kernel-development-with-
> > openembedded
> > 
> > I would like a way to develop inside Openembedded, but not in work
> > directory.
> > I mean to develop a project in a git tree, allowing me to use 'git diff'
> > ..... and finally 'git push' to my internal git servers.
> > This is an idea:
> > bitbake -c devshell-path /home/myapplication myapplicationrecipe
> > 
> > Perhaps srctree is a good tool already done for it?
> > 
> > Thanks,
> > Raffaele
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> 
> -- 
> Vladimir Davydov
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2010-05-27 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 14:42 developmet setup Vladimir Davydov
2010-05-27 17:16 ` Denys Dmytriyenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-26  6:34 Raffaele Recalcati
2010-05-26 11:19 ` Koen Kooi
2010-05-27 12:46   ` Raffaele Recalcati
2010-05-27 13:14 ` Antonio Ospite
2010-05-27 13:46   ` Raffaele Recalcati
2010-05-27 15:50 ` Enrico Scholz

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=20100527171607.GK23464@denix.org \
    --to=denis@denix.org \
    --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