Kontron ATOM Platform-512MB of Flash / Re: RealPlayer lpia Package / Self Contained Application
Daniel Yek <[email protected]>
| Newsgroups | gmane.comp.multimedia.helix.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Youcef, > ...I managed to just copy the opt directory by hand to the target > (Kontron ATOM Platform-512MB of Flash) > My platform will be in a closed network playing just H264 and MPEG4 > streams... I don't think I need Windows Media decoders... The product > is an embedded system that runs on an ATOM CPU... > Yes, I am trying to have the build as small as possible because I am > living on a 512MB of flash with many other applications such as > mozilla stuff... Thanks for the information. That sounds great! -- Daniel Yek. youcef chaoua wrote: > Hi Daniel, > > Thanks a lot for your swift replies... > Answers an comments are embedded below... > > On Tue, Nov 11, 2008 at 2:17 PM, Daniel Yek <[email protected] > <mailto:[email protected]>> wrote: > > > youcef chaoua wrote: > > Hi Daniel, > > Thank you... It finally built what I wanted... It seems that > the starting in clean directory helped... > > > That is pretty good. > > Now I have a problem installing it on a Moblin platform... it > complains about "lpia" ... is there an option to make lpia > packages and not 386/586? > > > Is the following good enough for you or now? > dpkg --force-architecture -i package.deb > > > It might work... I will try it later... Because I managed to just copy > the opt directory by hand to the target (Kontron ATOM Platform-512MB > of Flash)... It missed few codec files (2) and the Bin/Setup binary... > but that was fine because the codecs I am using are present (H264 & > MPEG4)... > > > If not, you can try converting it as shown in the following thread > that you posted. > > We have more work to do to support lpia. > > I tried this method > http://ubuntuforums.org/showthread.php?p=6058820 that seems to > be working so far but I don't know if this is enough !!! > > Is there a way to build it with size optimization as a self > contained application that depends on no external libs ? (the > smallest possible with no dependencies) > > > Is the official version <http://www.real.com/linux> posting too > much limitation for your purpose? It contains Windows Media > decoders, etc., that you can't build from source. (Is that for > personal use on a Dell Inspiron Mini or for redistribution on a > company's device/product?) > > > My platform will be in a closed network playing just H264 and MPEG4 > streams... I don't think I need Windows Media decoders... The product > is an embedded system that runs on an ATOM CPU... > > > By external libs, did you mean not having plugins? Or the runtime > environment on a Linux distribution/build? > > > I meant the runtime environment... > > > The RealPlayer for Linux project is mainly focusing on the > desktop, so we are not spending much time optimizing it for > embedded devices. I suppose it should still be acceptable to run > on Dell Inspiron Mini, or are you trying to reduce as much disk > usage as possible on the small (3.5 GB) storage device? > > > Yes, I am trying to have the build as small as possible because I am > living on a 512MB of flash with many other applications such as > mozilla stuff... > > > Someone would have to spend some time changing the compiler > switches and other build configurations and test it to optimize it > more. Depending on what you are trying to accomplish, it can be > just a change of compiler switches, or it can be a time consuming > task (says to have no plugin .so files at all and test). > > The easy changes are: > 1. create a release build, instead of a debug build that you tried: > Press ribosome menu #5! > [5] Toggle release (-trelease) > > 2. Adapt GCC compiler and linker options as you wish: > $BUILD_ROOT/umakecf/gcc.cf <http://gcc.cf> > or other files in the same directory. > > Helix client itself, that is the basis of RealPlayer for Linux, is > more adaptable to embedded devices and widely used for that purpose. > > > I will try these tips... Thanks again... > > > -- > Daniel Yek. > > > BTW, here is my successfull build result... > > Build complete in 67:51, 0 of 171 modules failed. > > Build System Menu > Ribosome v2.5 > -> Current Directory: /home/dev400t/HelixDev/helix > [0] Set BIF branch (realplay_gtk_current) > [1] Set Target(s) (player_all) > [2] Set Profile > (/home/dev400t/HelixDev/build/umakepf/helix-client-all-defines) > [3] run: build > [4] Toggle make depend & makefiles (-e -n) > [5] Toggle release (-trelease) > [6] Toggle 'make clean' (-c) > [7] Toggle clobber (Dangerous!) (-C) > [8] Toggle halt-on-error (-p green) > [9] Toggle verbose mode (-v) > [10] Toggle static build (-tnodll) > [11] Checkout source for selected target now > [12] Set Tag/Branch/Timestamp > [13] Help Page (full help in build/doc/index.html) > [14] run history: build > [Q] Quit > > Best regards, > Youcef > > On Mon, Nov 10, 2008 at 7:08 PM, Daniel Yek <[email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > Hi Youcef, > > Lets include helix-client-dev whenever possible, so that others > can help you too. > > > > youcef chaoua wrote: > > Hi Daniel, > > Thanks for your reply... I followed the getting started > by the > word... Still nothing... > > > After agreeing to the BEULA, it takes 4 hours or more to take > effect. You will then have access to distribution binaries (for > personal use) that enable you to play non-open-source media > formats. > > > I read the sources and it seems that it is compiling as > if it > was for a MAC!!! How is BEULA related to this? > > in /pthreadthreads.h > ... > /#ifndef _MAC_UNIX > struct HXsem_t : public sem_t > { > char padding[64]; /* Flawfinder: ignore */ // > different > linux versions have different binary reps blechhhh! > }; > #endif > ... > > > BEULA has nothing to do with this. > > Usually, the only time you get this when building Helix or > RealPlayer is when you used the wrong Ribosome build > settings (or > more specifically, built the wrong product). However, the > settings > you sent was correct. Could it be that when you changed > your build > (BIF Branch, for example), you didn't start in a clean > directory? > That would cause Ribosome to not check out modules that already > exist and mix source code from different branches. > > If the following command doesn't show the following output > for a > realplay_gtk_current build, then your source tree wasn't > checked > out cleanly and correctly: > > $ cvs status common/system/pub/platform/unix/pthreadthreads.h > ... > Sticky Tag: hxclient_1_5_0_cayenne > > So, whenever you switch to a different BIF Branch, start in a > clean directory. > > > Is there a way to compile it with a regular make > command from > downloaded sources and bypass all this python build > system ? > > > Once you know how to use Ribosome correctly, you will encounter > much fewer problems. We always build using Ribosome. Ribosome > manages proper checkout of source modules, generating > Makefiles, > compiler settings, etc. > > -- Daniel Yek. > > > > > Best regards, > Youcef > > > On Mon, Nov 10, 2008 at 4:35 PM, Daniel Yek > <[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>>> wrote: > > Hi, > > 1- there is a date warning for BIF!!! > /[WARNING] bif > > parser(/home/dev400t/build/bif-cvs/helix/client/build/BIF/realplay_gtk_current.bif > near beginning in <build>): This BIF file lacks an > expiration > date, using 2005-01-01/ > > > Please ignore this. > > I believe Ribosome designed the expiration mechanism so > that old > BIF files can retire from its menu without deleting > the BIF > files > from CVS repositories. Other than that, I haven't found > this lack > of expiration warning (noise) to have any impact. > > 2- there is a compiler version warning about gcc and > g++ 4.2.4 > / **WARNING** > gcc version is 4.2.4, not 3.* as expected. > g++ version is 4.2.4, not 3.* as expected./ > > > I am using gcc 4.3 now. I don't think gcc 4.2 is a > problem in > building the product. > > 3- It fails to grab th e files then says RESULT > = TRUE!!! > /getting distribution="protocol_dist/rtsp" (cvs > tag="hxclient_1_5_0_cayenne", root="helix", > dist_id="linux-2.2-libc6-gcc32-i586") > TESTING distribution/linux-2.2-libc6-gcc32-i586 > running 'cvs -d > > :ext:[email protected]:/cvsroot/distribution > checkout -l -d dir_cache_test > linux-2.2-libc6-gcc32-i586' in > '/home/dev400t/helix' (as = > 'tmpdir_-1210541888/dir_cache_test') > cvs checkout: warning: cannot write to history file > /cvsroot/distribution/CVSROOT/history: > Permission denied/ > > > As Eric said, you haven't agreed to the BEULA. > > Please follow the QuickStart more closely: > https://player.helixcommunity.org/2007/dev/ > > [0] Set BIF branch (realplay_gtk_current) > [1] Set Target(s) (player_all) > [2] Set Profile > > (/home/dev400t/build/umakepf/helix-client-all-defines) > > > These settings are correct. > > -- Daniel Yek. > > > > Eric Hyche wrote: > > It looks like it has failed to check out the > distribution > libraries. > The usual cause for this is that the BEULA has > not been > agreed to. > Here's the link to the BEULA: > > https://helixcommunity.org/beula/ > > Have you clicked that you agree to the BEULA? > > Eric > > ======================================= > Eric Hyche ([email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>>) > > Principal Engineer > RealNetworks, Inc. > > -----Original Message----- > From: > [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> > > [mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>] > On Behalf Of youcef chaoua > Sent: Thursday, November 06, 2008 6:07 PM > To: [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> > Subject: [Helix-client-dev] realplay_gtk_current > fails to > build on ubuntu... > > Hi, > > Can anyone please, tell me what is going > wrong with > this > build (build.out is attached)??? > > 1- there is a date warning for BIF!!! > [WARNING] bif > > parser(/home/dev400t/build/bif-cvs/helix/client/build/BIF/realplay_gtk_current.bif > near > beginning in <build>): This BIF file lacks an > expiration > date, using 2005-01-01 > > 2- there is a compiler version warning about gcc > and g++ 4.2.4 > **WARNING** > gcc version is 4.2.4, not 3.* as expected. > g++ version is 4.2.4, not 3.* as expected. > > 3- It fails to grab th e files then says > RESULT = > TRUE!!! > getting distribution="protocol_dist/rtsp" (cvs > tag="hxclient_1_5_0_cayenne", root="helix", > dist_id="linux-2.2-libc6-gcc32-i586") > TESTING distribution/linux-2.2-libc6-gcc32-i586 > running 'cvs -d > > :ext:[email protected]:/cvsroot/distribution > checkout -l -d > dir_cache_test linux-2.2-libc6-gcc32-i586' in > '/home/dev400t/helix' (as = 'tmpdir_- > 1210541888/dir_cache_test') > cvs checkout: warning: cannot write to > history file > /cvsroot/distribution/CVSROOT/history: > Permission > denied > cvs checkout: Updating dir_cache_test > cvs checkout: failed to create lock > directory for > > `/cvsroot/distribution/linux-2.2-libc6-gcc32-i586' > > (/cvsroot/distribution/linux-2.2-libc6-gcc32-i586/#cvs.lock): > Permission denied > cvs checkout: failed to obtain dir lock in > repository > `/cvsroot/distribution/linux-2.2-libc6-gcc32- > i586' > cvs [checkout aborted]: read lock failed - > giving up > RESULT => True > > And it keeps going like this... > > 4- Then alot of compilation warning!!! > (parentheses, not > used, deprecated...) and even worse, > compilation errors: > In file included from siteplug.cpp:94: > ../sitelib/pub/platform/unix/unixsite.h:77: > error: > 'Window' does not name a type > > Build System Menu > -> Current Directory: /home/dev400t/helix > [0] Set BIF branch (realplay_gtk_current) > [1] Set Target(s) (player_all) > [2] Set Profile > > (/home/dev400t/build/umakepf/helix-client-all-defines) > [3] run: build > [4] Toggle make depend & makefiles (-e -n) > [5] Toggle release (-trelease) > [6] Toggle 'make clean' (-c) > [7] Toggle clobber (Dangerous!) (-C) > [8] Toggle halt-on-error (-p green) > [9] Toggle verbose mode (-v) > [10] Toggle static build (-tnodll) > [11] Checkout source for selected target now > [12] Set Tag/Branch/Timestamp > [13] Help Page (full help in > build/doc/index.html) > [Q] Quit > Enter selection or flags: 3 > > A quick reply is highly appreciated. > > Thanks in advance... > > Best regards, > Youcef > > >