2015/12/24/ 03:54,"Robert Nelson" <[email protected]>wrote:
>
> On Wed, Dec 23, 2015 at 1:46 PM,  <[email protected]> wrote:
> > Hi, Everyone:
> >
> > I'm going to setup a cross-toolchain of BBB for developers using CentOS
or
> > Windows.
> >
> > I have read the Cross Toolchain for Debian Wheezy, which told about
creating
> > the cross-toolchain. But it did not find a way to generate the sysroot.
The
> > sysroot should include all the libraries and headers that I need to
> > distribute. I think it has to be created in some way. Anyone can share
> > something useful to build the sysroot?
>
> One of the big issues with wheezy, it had fairly old libc, so any of
> the pre-built linaro toolchains are just going to cause issues..
Yes, that's why i am trying to build such a toolchain. I have not looked
into your script for wheezy. Is that workable?

>
> So for 'wheezy' it's just best to build on an armhf machine..
>
> Now if you switch to jessie on the bbb. Jessie's multi-arch was much
> better, so you can install debian jessie on your x86 and install all
> the *armhf* libraries via apt..
Since my customers insisted to use windows or CentOS as their dev env, how
can I make a tarball of the toolchain and sysroot and run it on CentOS and
Windows, no matter Wheezy or Jessie? For sysroot, how can i select
necessary libs and headers? I did not find any useful information or
discussion on creating sysroot that needs some customization.

>
> here are the jessie cross toolchains:
>
> http://www.emdebian.org/News/2014/20141025.html
>
> In stretch it'll even be easier to cross..
I am new for BBB. How stable is Jessie comparing with Wheezy? I am building
commercial product so stability is the most important thing. But anyway, we
will do evaluation.

Thanks!
dlw

>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to