• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 300 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM6442: Missing meta-oe recipes from TISDK Arago

AM6442: Follow-up on emacs - it appears to be included in Kirkstone?

Braden Hines
Intellectual 370 points
Part Number: AM6442


Following up on my question about emacs, I see that OpenEmbedded does include emacs_27.2.bb in the kirkstone release.

I've also seen a lot of activity in the TI repositories around kirkstone.

If I pull down arago-kirkstone-config.txt and work with that, am I likely to be successful, or is it still too green?  

(Related question - I've been trying to understand what the "-next" suffix means.  I would guess that the base kirkstone or dunfell is likely to work but that the "-next" is untested?  I see -next in both the TI and OpenEmbedded repositories, but I've not found any description in the FAQs.)

Thanks,

Brad

  • 0
    TI__Guru 69817 points

    Hi Braden,

    I just double-checked, indeed, the emacs package was re-introduced for Kirkstone! So sounds like your wish of being able to run emacs on AM64x may become reality! As for Kirkstone, we are doing R&D work at the moment to migrate/enable support for our devices on that Yocto version, which will become official with one of the next SDK releases. Until this is official (meaning work is complete, all kinks are ironed out, and the solution is fully tested, qualified & deemed good for production) I'd however discourage you from trying to use any Kirkstone branches. It's also not something we'd be able to support at this time.

    However if you must have emacs you might be able to backport the associated recipes to Dunfell without too much trouble I suppose.

    As for the "-next" suffix on some branch names, those usually denote an integration (staging) branch to merge/test new features and fixes, before those get then merged into the corresponding "master branch. That's a common thing amongst many open source projects.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Intellectual 370 points

    Thanks, Andreas.  I will watch for Kirkstone in an upcoming release.