•   
  • 1
  • 103
  • 104
  • 105(current)
  • 106
  • 107
  • 119
  •   
RaspBMC Kodi/XBMC test builds
(2014-11-01, 13:17)miappa Wrote: Someone knows where I can get libcec 2.2.0 + headers?

This looks like the 2.2.0 tag:
https://github.com/Pulse-Eight/libcec/tr...2.0-repack
Reply
Hehe... thanks. I was looking for a separate branch, didn´t even think about looking at the tags.
You learn something new every day! Wink

Silly question perhaps, but does tags work the same as branches when cloning?
Edit: Nevermind the last question, a fast google and I had the answer....
Reply
I can´t get past this error.
As far as I can see I have compiled the latest version of libcec (directly on Pi) and added it to my buildroot, but no matter what I do it still says "configured version 2:1:0" and libcec.pc also says 2.1.0.
I compared to latest commits and they are there...?

Obviously I am doing something wrong... any tips?
And can that error be something else too?
Reply
(2014-11-01, 13:17)miappa Wrote:
Code:
PeripheralCecAdapter.cpp:1293:19: error: 'CEC::libcec_configuration' has no member named 'iButtonRepeatRateMs'

Are you using latest newclock4 build?

That has no code on line 1293. You should see this code near here;
Code:
#if defined(CEC_DOUBLE_TAP_TIMEOUT_MS_OLD)
  m_configuration.iDoubleTapTimeout50Ms = config.iDoubleTapTimeout50Ms;
  bChanged |= SetSetting("double_tap_timeout_ms", (int)m_configuration.iDoubleTapTimeout50Ms * 50);
#else
  m_configuration.iDoubleTapTimeoutMs = config.iDoubleTapTimeoutMs;
  bChanged |= SetSetting("double_tap_timeout_ms", (int)m_configuration.iDoubleTapTimeoutMs;
#endif

and CEC_DOUBLE_TAP_TIMEOUT_MS_OLD should be defined from libcec, so it should be referring to iDoubleTapTimeout50Ms not iDoubleTapTimeoutMs.
Reply
Yes, latest newclock4 (cloned jsut recently, after your last commits).
And this is a copy of the cloned PeripheralCecAdapter.cpp: http://pastebin.com/2apH3YD7
1293 is that #else in the middle of what you just posted.
And just in case, I checked the clone command I used: git clone https://github.com/popcornmix/xbmc --branch newclock4 --single-branch

It has to do something with libcec not being correct version, right? All latest commits seems to be there but it still says 2.1.0...
Tried to checkout the libcec 2.2.0 tag, compile from "release" tree (as it looked the same), make my own branch, but still 2.1.0.
I don´t know git that well so I am probably doing something wrong. What would be the correct way to clone and build a tagged version?

I gotta take off soon, will play around with this some more tomorrow.
Reply
(2014-11-01, 18:20)miappa Wrote: 1293 is that #else in the middle of what you just posted.

If gcc gives a warning line number that doesn't contain code, I'd suggest you are not compiling the version of the code that you think you are.
You would get that error message from previous xbmc master version of the code.

A big CEC PR has just been merged and I've rebased newclock4 on it, so it may be worth trying again.
Reply
It seems you need to clone libcec from https://github.com/popcornmix/libcec/tree/libcec-2.2.0 or apply that on top of PulseEight's.
Reply
I would be very surprised if I am compiling the wrong version as I have tried it manually 3 times + 3 times with my scripts that I have used for a long time.
I also compared to this and they look identical, so the code is #else is there?
But maybe I am missing something, will look into it more tomorrow.
Thanks for the help so far.

Edit:
@menakite
Haven´t tried that (or seen it), thanks for the tip.
Reply
(2014-11-01, 13:17)miappa Wrote: Also, I got Kodi(.bin) running quite easily, only had to add+disable some jobs and modify some scripts.
If someone is interested I could try to make a simple how-to and some simple scripts.

Very interested!
Media Companion Dev.
Media Companion - Kodi / XBMC - Media Companion
Reply
I indeed needed to use popcornmix´s libcec tree when compiling libcec, Kodi built fine now.
Just in case I tested with opdenkamps version first and I had the same error.

Have a new build now, will post a how-to to enable Kodi + the new build shortly.
Reply
ONLY FOR THE BRAVE!
Please note that there have been some changes. The job is now back to being called 'xbmc'. I recommend that you re-download all scripts if you are uncertain.

To be able to run Kodi builds on Raspbmc after the recent rebranding commits some things needs to be modified.
What needs to be done is simply edit some upstart jobs + edit the watchdog script.

I recommend that you backup the original files first (see below), this in case you have to revert and you for some reason don´t have an internet connection.
I have made some simple scripts which you can use if you want to switch between XBMC builds and Kodi builds.

The following will backup the original files + download the scripts.
Code:
sudo cp /etc/init/delay-start-50.conf /etc/init/delay-start-50.conf.bak
sudo cp /etc/init/xbmc.conf /etc/init/xbmc.conf.bak
sudo cp /scripts/xbmc-watchdog.sh /scripts/xbmc-watchdog.sh.bak
wget http://goo.gl/LWwLDe --no-check-certificate -O enable-kodi1.sh
wget http://goo.gl/G4EG8M --no-check-certificate -O enable-kodi2.sh
wget http://goo.gl/yUR9KO --no-check-certificate -O enable-xbmc.sh

NB!
There are sveral enable-kodi scripts due to changes in Kodi master!
For example, enable-kodi1.sh is only for Nov 02 and Nov 03 builds. I will keep it this way in case there will be more changes.
It will be stated in each build-post which script that should be used.

To enable Kodi builds, simply run:
Code:
sudo sh enable-kodi*.sh
Where * is mentioned in the build-post.

And to enable older XBMC or release build, run:
Code:
sudo sh enable-xbmc.sh

Please note that XBMC/Kodi will not start if you have enabled Kodi but trying to run XBMC and vice versa.
If you for example want to revert to the release version, run ’sudo sh enable-xbmc.sh’ + delete the .xbmc-current link.
If you end up with a broken setup where Kodi or XBMC does not start, don´t worry. Just run the correct enable-script and reboot.

NB!
The userdata folder is now named .kodi, but I included a symlink command in the enable-kodi script so you can more easily switch between builds.
But have in mind that if you run a Kodi build the correct userdata directory is now ’.kodi’.
And the log is obviously called kodi.log.

NB! Note that I have reverted and the job is called "xbmc" once again!
Code:
sudo initctl start xbmc
sudo initctl stop xbmc
Reply
NOTE: PR:5588 enabled a lot of component debug logging and you probably want to turn this off as the log will grow quite fast.
You disable this in Settings - System - Debugging (uncheck Enable component-specific logging).

Updated Helix build, Kodi master from Nov 01 + newclock4 commits.

Kodi Master:
Master changelog
• [CEC] bump libCEC to 2.2.0 + several more CEC related commits
• A lot of newclock4 features has now gone into master

Newclock4 additions:
• [mmalrenderer] Add choice of 3 deinterlace schemes
• [omxcore] Skip out of flush on error
• [SinkPi] Handle multichannel layout more like OMXAudio
• [rbp] Default extract thumbnails to false
• [cec] Add settings for configuring button repeats

An interesting new feature to test is the new repeat settings for CEC.
You find this in Settings - System - Input devices - Peripherals - CEC Adapter.

GPU firmware from Nov 01 included:
• arm_loader: Add lock to rotated frame updates to avoid an unsafe update from mailbox channel
• hdmi: Fix for attached flag in hdmi status when booting with cable disconnected

NB! To be able to run this build you must first run enable-kodi*.sh as explained here!

For this build you will need the enable-kodi1 script.
Code:
wget http://goo.gl/LWwLDe --no-check-certificate -O enable-kodi1.sh
sudo sh enable-kodi1.sh

To install Kodi build, SSH to Pi (first run ’sudo enable-kodi1.sh’ if not already enabled):
Code:
wget -O kodi-14-20141102-nc4.tar.gz http://goo.gl/aIyAEr --no-check-certificate
pv kodi-14-20141102-nc4.tar.gz | tar xzf - -C /home/pi/.upgrade
sudo cp /home/pi/.upgrade/kodi-14-20141102-nc4/{fixup_x.dat,start_x.elf} /boot
ln -sfn /home/pi/.upgrade/kodi-14-20141102-nc4/xbmc-bcm /home/pi/.xbmc-current
sudo reboot

See post #1 for more info
Reply
(2014-11-02, 14:54)miappa Wrote: Updated Helix build, Kodi master from Nov 01 + newclock4 commits.

Kodi Master:
Master changelog
• [CEC] bump libCEC to 2.2.0 + several more CEC related commits
• A lot of newclock4 features has now gone into master

Newclock4 additions:
• [mmalrenderer] Add choice of 3 deinterlace schemes
• [omxcore] Skip out of flush on error
• [SinkPi] Handle multichannel layout more like OMXAudio
• [rbp] Default extract thumbnails to false
• [cec] Add settings for configuring button repeats

An interesting new feature to test is the new repeat settings for CEC.
You find this in Settings - System - Input devices - Peripherals - CEC Adapter.

GPU firmware from Oct 17 included:
• arm_loader: Add lock to rotated frame updates to avoid an unsafe update from mailbox channel
• hdmi: Fix for attached flag in hdmi status when booting with cable disconnected

NB! To be able to run this build you must first run enable-kodi.sh as explained here!

To install Kodi build, SSH to Pi (first run ’sudo enable-kodi.sh’ if not already enabled):
Code:
wget -O kodi-14-20141102-nc4.tar.gz http://goo.gl/aIyAEr --no-check-certificate
pv kodi-14-20141102-nc4.tar.gz | tar xzf - -C /home/pi/.upgrade
sudo cp /home/pi/.upgrade/kodi-14-20141102-nc4/{fixup_x.dat,start_x.elf} /boot
ln -sfn /home/pi/.upgrade/kodi-14-20141102-nc4/xbmc-bcm /home/pi/.xbmc-current
sudo reboot

See post #1 for more info

This is fantastic work. Before I try this build on my test pi (currently running kodi-14-20141019-nc4) what is the status of the PVR clients in this build, specifically mythtv client which I have a requirement for in my setups and which works in the 19th October version, but does not work in the Ubuntu nightly versions since about the middle of the month?

I have been rsyncing the /boot directory into the root of each upgrade version to enable me to revert to the previous version should the system/firmware/config not be stable. I can then return to a previous version by changing the link to point at a previous version and rsyncing back the relevent /boot. I understand that by removing the link altogether I would be back to the stable RaspBMC release. What would be your advice as to how to setup this restore mechanism and do you use a similar mechanism.

Cheers Spart
6 x Raspberry Pi Model B & B+ Pi2 & 3 Zotac Mag Ubuntu 14.04.1 - Ubuntu 14.04.1 Test Machine Kodi Nightly - RocketNAS 8TB Usable Raid 6 Ubuntu 14.04.1 RocketNAS Build
Reply
Regarding PVR addons, I always compile the latest from opdenkamps (maser) git: https://github.com/opdenkamp/xbmc-pvr-addons
I see that mythtv was updated on the 20th of october, so it is diffrent from laast build from the 19th.
My guess is that the version you use on Ubuntu is before the xbmc.gui sync commits, see here: https://github.com/opdenkamp/xbmc-pvr-ad...its/master
I guess you have to test to make sure, I don´t use PVR at all myself so cannot test.

Regarding /boot, there really is nothing else than the gpu firmware files (fixup_x.dat & start_x.elf) that is updated in my builds. Everything else is the same as stock Raspbmc release.
So I don´t bother with any sort of backup, if I need to revert I download those files from git (old versions) or I download the Raspbmc filesystem tarball and replace the files.
Reply
I think the enable-kodi needs to be modified there isn't any directory called scripts or a person would need to make a directory called scripts "sudo mkdir scripts"
Reply
  •   
  • 1
  • 103
  • 104
  • 105(current)
  • 106
  • 107
  • 119
  •   
 
Thread Rating:
  • 15 Vote(s) - 4.4 Average



Logout Mark Read Team Forum Stats Members Help
RaspBMC Kodi/XBMC test builds4.415