_ running '/usr/bin/python src/build/gyp_chromium' in '/home/pi/raspberry/berkelium/build/chromium'įile "src/build/gyp_chromium", line 143, in įile "src/tools/gyp/pylib/gyp/_init_.py", line 445, in mainįile "src/tools/gyp/pylib/gyp/_init_.py", line 84, in Loadĭepth, generator_input_info, check, circular_check)įile "src/tools/gyp/pylib/gyp/input.py", line 2174, in Loadįile "src/tools/gyp/pylib/gyp/input.py", line 421, in LoadTargetBuildFileįile "src/tools/gyp/pylib/gyp/input.py", line 355, in LoadTargetBuildFileįile "src/tools/gyp/pylib/gyp/input.py", line 210, in LoadOneBuildFile
IMPORT ERROR LIBAVG MODULE INSTALL
It failed to install and gave the following errors: I ran util/build-chromium.sh instead of build_chromium.sh. I have made it work before but forgot to write down the steps. On the side of the new image, still building and running into trouble getting the new V8 compiled in. I installed the client in my home folder.
IMPORT ERROR LIBAVG MODULE DOWNLOAD
Download it into the libavg folderĮverything is now ready to install a Xibo 1.4 client. Sudo ln -s /usr/lib/python2.7/dist-packages/libavg/avg.so.0.0.0 avg.so.0ĭue to the fact that the Xibo Python client is written against an older version of libavg it requires an animation class which isn't shipped with libavg anymore. The only thing that we need to do to finish this installation is making sure every library can find the avg.so library, which is not inside the normal library search path.
To do this you will need to copy the contents of the install_release folder to the /usr folder of the machine. You are now ready to install all the compiled libraries on to the Raspberry that will run the Xibo client code. So in our install_release folder we move it from site_packages to dist_packages.Ĭd ~raspberry/install_release/lib/python2.7 Only thing here is that it is installed as a site-package and we would like to have it installed in the dist-packages. Afterwards everything gets installed in our install_release folder. Now libavg gets build with the browsernode plugin included in the code. Lower in the howto you will find installation steps.Īfter the 'make install' command in the ~/raspberry/libavg directory everything is installed into the ~/raspberry/install_release/ directory.įrom there you should do the following to install libavg on your system : It will take down the you give me an overview of the video functions and how they incorporate HWAccel in libAVG? Once I am done with this build I will give OpenMAX a steps you are refuring to are build steps and not installation steps.
This means that date and time functions will work in the webpage javascripts.Īfter that I will start at the new version of libavg which I presume will not give me a think you didn't install libavg in the correct location or forgot to symlink it in you only need a client you can stop/remove mysql and apache. I have corrected that and now I am in the middle of recompiling Berkelium with the new V8 and V8-I18N support. As you would expect it didn't work because i forgot to document a few steps. Which isn't a bad thing since it gave me the opportunity to check my howto with the new V8 parts. Thanks to all the compiling i ran through a second 32GB SDCard in one year and had to start over again. I am currently in the middle of building the new version of berkelium, libavg and Xibo. But this requires some more patching then already in my script. It will take some time to complete this as I also will implement a newer V8 ( javascript ) enigine into Berkelium so date and time functions will work.
In the meantime I will be building a new image, with the latest libAVG ( which is faster then the older version i have read ) and the 1.6 Xibo ( probably rc2 ). I will try and get people who know what they are talking about to help. the CPU is not op to the task to do this ( even if you overclock it ). As long as the hardware acceleration has not been implemented video will not run smooth on the RPi since every decoding stage has to be done by the main ARM processor and not the GPU. It is up to us as comminutty to fix this problem. As Uli wrote earlier he doesn't have the capability timewise to implement openMAX into LibAVG. I am sorry to say there is no solution to the video problem as of yet. I will reply in English so everybody can use this information.
0 kommentar(er)
