On Fri, Sep 12, 2014 at 4:08 PM, Ben Gamari <b...@smart-cactus.org> wrote:
> Robert Nelson <robertcnel...@gmail.com> writes:
>
>>
>> So the "-bone" is close to mainline (small # of patches). The "-ti" we
>> are a basing on a ti branch: (git.ti.com, patchset >20Mb).. Plus the
>> 'debian' linux-image-armmp will also work once we switch to jessie..
>> (you can even install ubuntu's linux-image *.deb) the bootloader will
>> find it.
>>
>> v3.14-ti repo: https://github.com/beagleboard/linux/tree/3.14
>>
> How do you go about generating the .debs? There doesn't appear any
> packaging in the beagleboard/linux tree and the .debs don't appear to
> have corresponding source debs.

We are using the in-tree "make deb-pkg"

After i push a tag to:

https://github.com/beagleboard/linux/

Like: 3.14.17-ti-r19

https://github.com/beagleboard/linux/tree/3.14.17-ti-r19

I'll fire off a native build (wheezy *.deb is built in a clean wheezy chroot)

fakeroot make -j5 ARCH=arm  LOCALVERSION=-ti-r19 CROSS_COMPILE=
KDEB_PKGVERSION=1wheezy KBUILD_DEBARCH=armhf deb-pkg

This generates:

linux-headers-3.14.17-ti-r19_1wheezy_armhf.deb
linux-image-3.14.17-ti-r19_1wheezy_armhf.deb
linux-libc-dev_1wheezy_armhf.deb

(and) (which i haven't enabled in the 3.14 branch)

linux-firmware-image-3.16.2-armv7-lpae-x2_1jessie_armhf.deb

linux-headers-*
linux-firmware-image-*
linux-image-*

get pushed to repos.rcn-ee.net (reprepro)

linux-libc-dev_1wheezy_armhf.deb -> /dev/null

So unfortunately the src package is not generated via "make deb-pkg"
thus we rely on the git tag's..

PS you can build a *.deb via cross on x86:

make -j5 ARCH=arm  LOCALVERSION=-git<sha>
CROSS_COMPILE=<bin/arm-cross-> KDEB_PKGVERSION=1cross
KBUILD_DEBARCH=armhf deb-pkg

Regards,

-- 
Robert Nelson
http://www.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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to