On Jun 29, 2013, at 11:17 AM, Charles Nicholson <charles.nichol...@gmail.com>
wrote:
> Thanks everyone for the quick response. Once we get things working, I'd be
> happy to contribute a page to the wiki about how to freeze and build
> Angstrom locally without further updates, if people think that would be
> helpful.
>
> (BTW, the build machine in question has no access to the outside internet,
> which might also be contributing to the errors I'm seeing? All git
> commands against github etc. fail…)
We strive to make it such that it doesn't have to enquire once you download. So
when you see that some recipe is
trying to query the sources from www you should check if it has
SRCREV set to a hardcoded git SHA sometimes it might have tagnames or AUTOREV
assigned to SRCREV
that will need to be changed to specific git commit SHAs
So that can be your first contribution.
>
> Best, and thanks again,
> Charles
>
>
> On Sat, Jun 29, 2013 at 7:17 AM, Khem Raj <raj.k...@gmail.com> wrote:
>
>>
>> On Jun 28, 2013, at 11:21 AM, Charles Nicholson <
>> charles.nichol...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> First off, thanks a lot for the Angstrom effort, it's a great distro and
>>> we're committing to use it on BeagleBone Blacks to manage our automated
>>> test rack at work.
>>>
>>> We are trying to figure out the best way to capture a full Angstrom
>>> codebase snapshot so that we can iterate locally on it and make private
>>> changes. I see that invoking "bitbake virtual/kernel" performs an update
>>> before doing a build, so our current strategy is failing.
>>
>> bitbake -cfetchall <yourimage>
>> will download the needed sources and then you can add BB_NO_NETWORK = "1"
>> to you local.conf from thereon it will not access web anymore
>>
>>>
>>> My naive first attempt to capture Angstrom was to pull it down and do a
>>> full build as per the instructions on the Angstrom site. After
>> confirming
>>> that this gave me a good output image, I deleted the entire /build
>>> directory, and then recursively deleted the .git metadata ("find . -type
>> d
>>> -name ".git" -exec rm -rf {}\;"). I committed the results to our local
>>> private git repository.
>>>
>>> When our build slave machine tries to sync and build, it gives us this:
>>>
>>> MACHINE=beaglebone ./oebb.sh bitbake console-image
>>
>>
>> dont se oebb.sh wrapper to run builds once you have create the sandbox.
>> using oebb.sh config then
>>
>> source ~/.oe/angstrom-* in your shell and after that issue normal bitbake
>> commands
>> directly
>>
>> bitbake sytemd-image and so on
>>
>> and once everything works for you. Contributions are welcome
>>
>>> col: write error
>>> grotty:<standard input> (<standard input>):25092:fatal error: output
>> error
>>> WARNING!!!!
>>> WARNING: bitbake is using a different uri
>>> 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
>>> layers.txt 'git://github.com/openembedded/bitbake.git'
>>> WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
>>> WARNING!!!!
>>> Fetching origin
>>>
>>>
>>> This makes sense, because the conf/layers.txt file references all of
>>> the subprojects on the public github.
>>>
>>>
>>> Can I tell bitbake to use the local versions? Do I need to host each
>>> subproject on our internal git and point layers.txt towards that? Is
>>> what I'm doing sensible? :)
>>>
>>>
>>> All advice, comments, flames welcome, and thanks for taking the time
>>> to read this.
>>>
>>>
>>> Best Regards,
>>>
>>> Charles Nicholson
>>> _______________________________________________
>>> Angstrom-distro-devel mailing list
>>> Angstrom-distro-devel@linuxtogo.org
>>>
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>>
>> _______________________________________________
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
