List Info

Thread: Creating a player binary package




Creating a player binary package
user name
2007-08-13 12:35:39
Checking up again with OLPC stuff.

So, right now I'm trying to set up a version of the player
that will
function without installation so we can have a functional
binary
package that can be copied directly onto the OLPC and run
with no
setup.

So, what file structure does hxplay require?  Specifically,
what
structure is necessary to play video?  What environment
variables are
set during run time?  That sort of thing.

I've already cp -r the share directory (player/app/gtk/res
there may
be another one I should be using)

Thank you,
Sarah Cooley

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

Re: Creating a player binary package
country flaguser name
United States
2007-08-13 13:15:55
Sarah Cooley wrote:
> Checking up again with OLPC stuff.
>
> So, right now I'm trying to set up a version of the
player that will
> function without installation 

The player works without installation if you execute the
realplay script at:
  player/installer/archive/temp/

Installation is meant to add desktop integration support,
etc. If you 
don't need desktop integration, you don't need the
post-installation 
scripts steps.

If what you want is really to perform desktop integration
within 
FirstRun, you can move the functionality in
post-installation scripts 
into the player itself.

(FirstRun refers to the setup steps performed if hxplayerrc
or 
realplayerrc file is not found, indicating that the player
is starting 
up for the first time after "installation".)

> so we can have a functional binary
> package that can be copied directly onto the OLPC and
run with no
> setup.
>
> So, what file structure does hxplay require? 
>   

The Umakefile that creates the player structure is:
/player/installer/archive/make_tempdir

You can start with the file structure created by
make_tempdir at:
  player/installer/archive/temp/
and add or eliminate whatever you need or don't need.

> Specifically, what structure is necessary to play
video?  

I don't think there is file structure special for video
playback; the 
above information should be sufficient.

Are you having problems with video playback? If so, what is
the 
difference between what you are working on and what is
already working 
for OLPC?

Are you having problems only with embedded player video
playback?

> What environment variables are set during run time? 
That sort of thing.
>   

Not sure what information you need, but it is best to
consult the source 
code and the realplay script.


-- 
Daniel Yek.


> I've already cp -r the share directory
(player/app/gtk/res there may
> be another one I should be using)
>
> Thank you,
> Sarah Cooley
>   

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

  
Re: Creating a player binary package
country flaguser name
United States
2007-08-13 13:15:55
Sarah Cooley wrote:
> Checking up again with OLPC stuff.
>
> So, right now I'm trying to set up a version of the
player that will
> function without installation 

The player works without installation if you execute the
realplay script at:
  player/installer/archive/temp/

Installation is meant to add desktop integration support,
etc. If you 
don't need desktop integration, you don't need the
post-installation 
scripts steps.

If what you want is really to perform desktop integration
within 
FirstRun, you can move the functionality in
post-installation scripts 
into the player itself.

(FirstRun refers to the setup steps performed if hxplayerrc
or 
realplayerrc file is not found, indicating that the player
is starting 
up for the first time after "installation".)

> so we can have a functional binary
> package that can be copied directly onto the OLPC and
run with no
> setup.
>
> So, what file structure does hxplay require? 
>   

The Umakefile that creates the player structure is:
/player/installer/archive/make_tempdir

You can start with the file structure created by
make_tempdir at:
  player/installer/archive/temp/
and add or eliminate whatever you need or don't need.

> Specifically, what structure is necessary to play
video?  

I don't think there is file structure special for video
playback; the 
above information should be sufficient.

Are you having problems with video playback? If so, what is
the 
difference between what you are working on and what is
already working 
for OLPC?

Are you having problems only with embedded player video
playback?

> What environment variables are set during run time? 
That sort of thing.
>   

Not sure what information you need, but it is best to
consult the source 
code and the realplay script.


-- 
Daniel Yek.


> I've already cp -r the share directory
(player/app/gtk/res there may
> be another one I should be using)
>
> Thank you,
> Sarah Cooley
>   

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

  
Re: Creating a player binary package
user name
2007-08-16 18:01:07
Ok, so I got /player/installer/archive working (it wasn't
before) but
am still running into problems.

First, hopefully this isn't a big discrepancy, cayenne_1_5_0
builds
/client/core/clntcore.so, atlas_3_1_0 (our new branch)
builds
hxmedplyeng.so instead of clntcore.so.  I modified the
make_tempdir to
account for this but hxplay won't run in
player/installer/archive so I
was thinking maybe that has a hand in it.
Any idea what the differences are between the two?

The error I'm getting is:

cooleysXanadu:~/helix/gecko_plugin/player/installer/archive/
temp$ ./hxplay

** (hxplay.bin:16468): WARNING **: HXPlayer: Error
0x80004005: "A
general error has occurred."

** (hxplay.bin:16468): WARNING **: Could not create helix
engine. Make
sure your helix libs are installed at:
HELIX_LIBS=/home/cooleys/helix/gecko_plugin/player/installer
/archive/temp


As far as video, I can't use the structure currently set up
on the
OLPC because the GUI front end was written in python ontop
of splay
and atlas which, as far as I know, won't work in an embedded
setting
(the plugin) with out a front end of some sort.

Any way, it's strange.  Hxplay runs in any directory where
all codecs
are present (with full functionality), plays audio
regardless and will
play audio in an embedded setting.  All of this is when
using the
hxplay script in debug, hxplay won't run at all in
/player/installer/archive/temp currently.

 --
Sarah Cooley


On 8/13/07, Daniel Yek <dyekreal.com> wrote:
>
> Sarah Cooley wrote:
> > Checking up again with OLPC stuff.
> >
> > So, right now I'm trying to set up a version of
the player that will
> > function without installation
>
> The player works without installation if you execute
the realplay script at:
>   player/installer/archive/temp/
>
> Installation is meant to add desktop integration
support, etc. If you
> don't need desktop integration, you don't need the
post-installation
> scripts steps.
>
> If what you want is really to perform desktop
integration within
> FirstRun, you can move the functionality in
post-installation scripts
> into the player itself.
>
> (FirstRun refers to the setup steps performed if
hxplayerrc or
> realplayerrc file is not found, indicating that the
player is starting
> up for the first time after "installation".)
>
> > so we can have a functional binary
> > package that can be copied directly onto the OLPC
and run with no
> > setup.
> >
> > So, what file structure does hxplay require?
> >
>
> The Umakefile that creates the player structure is:
> /player/installer/archive/make_tempdir
>
> You can start with the file structure created by
make_tempdir at:
>   player/installer/archive/temp/
> and add or eliminate whatever you need or don't need.
>
> > Specifically, what structure is necessary to play
video?
>
> I don't think there is file structure special for video
playback; the
> above information should be sufficient.
>
> Are you having problems with video playback? If so,
what is the
> difference between what you are working on and what is
already working
> for OLPC?
>
> Are you having problems only with embedded player video
playback?
>
> > What environment variables are set during run
time?  That sort of thing.
> >
>
> Not sure what information you need, but it is best to
consult the source
> code and the realplay script.
>
>
> --
> Daniel Yek.
>
>
> > I've already cp -r the share directory
(player/app/gtk/res there may
> > be another one I should be using)
> >
> > Thank you,
> > Sarah Cooley
> >
>
>

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

Re: Creating a player binary package
user name
2007-08-16 18:01:07
Ok, so I got /player/installer/archive working (it wasn't
before) but
am still running into problems.

First, hopefully this isn't a big discrepancy, cayenne_1_5_0
builds
/client/core/clntcore.so, atlas_3_1_0 (our new branch)
builds
hxmedplyeng.so instead of clntcore.so.  I modified the
make_tempdir to
account for this but hxplay won't run in
player/installer/archive so I
was thinking maybe that has a hand in it.
Any idea what the differences are between the two?

The error I'm getting is:

cooleysXanadu:~/helix/gecko_plugin/player/installer/archive/
temp$ ./hxplay

** (hxplay.bin:16468): WARNING **: HXPlayer: Error
0x80004005: "A
general error has occurred."

** (hxplay.bin:16468): WARNING **: Could not create helix
engine. Make
sure your helix libs are installed at:
HELIX_LIBS=/home/cooleys/helix/gecko_plugin/player/installer
/archive/temp


As far as video, I can't use the structure currently set up
on the
OLPC because the GUI front end was written in python ontop
of splay
and atlas which, as far as I know, won't work in an embedded
setting
(the plugin) with out a front end of some sort.

Any way, it's strange.  Hxplay runs in any directory where
all codecs
are present (with full functionality), plays audio
regardless and will
play audio in an embedded setting.  All of this is when
using the
hxplay script in debug, hxplay won't run at all in
/player/installer/archive/temp currently.

 --
Sarah Cooley


On 8/13/07, Daniel Yek <dyekreal.com> wrote:
>
> Sarah Cooley wrote:
> > Checking up again with OLPC stuff.
> >
> > So, right now I'm trying to set up a version of
the player that will
> > function without installation
>
> The player works without installation if you execute
the realplay script at:
>   player/installer/archive/temp/
>
> Installation is meant to add desktop integration
support, etc. If you
> don't need desktop integration, you don't need the
post-installation
> scripts steps.
>
> If what you want is really to perform desktop
integration within
> FirstRun, you can move the functionality in
post-installation scripts
> into the player itself.
>
> (FirstRun refers to the setup steps performed if
hxplayerrc or
> realplayerrc file is not found, indicating that the
player is starting
> up for the first time after "installation".)
>
> > so we can have a functional binary
> > package that can be copied directly onto the OLPC
and run with no
> > setup.
> >
> > So, what file structure does hxplay require?
> >
>
> The Umakefile that creates the player structure is:
> /player/installer/archive/make_tempdir
>
> You can start with the file structure created by
make_tempdir at:
>   player/installer/archive/temp/
> and add or eliminate whatever you need or don't need.
>
> > Specifically, what structure is necessary to play
video?
>
> I don't think there is file structure special for video
playback; the
> above information should be sufficient.
>
> Are you having problems with video playback? If so,
what is the
> difference between what you are working on and what is
already working
> for OLPC?
>
> Are you having problems only with embedded player video
playback?
>
> > What environment variables are set during run
time?  That sort of thing.
> >
>
> Not sure what information you need, but it is best to
consult the source
> code and the realplay script.
>
>
> --
> Daniel Yek.
>
>
> > I've already cp -r the share directory
(player/app/gtk/res there may
> > be another one I should be using)
> >
> > Thank you,
> > Sarah Cooley
> >
>
>

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

Re: Creating a player binary package
country flaguser name
United States
2007-08-16 18:36:00
Sarah Cooley wrote:
> Ok, so I got /player/installer/archive working (it
wasn't before) but
> am still running into problems.
>
> First, hopefully this isn't a big discrepancy,
cayenne_1_5_0 builds
> /client/core/clntcore.so, atlas_3_1_0 (our new branch)
builds
> hxmedplyeng.so instead of clntcore.so.  I modified the
make_tempdir to
> account for this but hxplay won't run in
player/installer/archive so I
> was thinking maybe that has a hand in it.
> Any idea what the differences are between the two?
>
> The error I'm getting is:
>
> cooleysXanadu:~/helix/gecko_plugin/player/installer/archive/
temp$ ./hxplay
>
> ** (hxplay.bin:16468): WARNING **: HXPlayer: Error
0x80004005: "A
> general error has occurred."
>
> ** (hxplay.bin:16468): WARNING **: Could not create
helix engine. Make
> sure your helix libs are installed at:
>
HELIX_LIBS=/home/cooleys/helix/gecko_plugin/player/installer
/archive/temp
>   

Does the following run?
cd
/home/cooleys/helix/gecko_plugin/player/installer/archive/te
mp
HELIX_LIBS=.  ./hxplay

(Note the dot following equal sign.)

> As far as video, I can't use the structure currently
set up on the
> OLPC because the GUI front end was written in python
ontop of splay
> and atlas which, as far as I know, won't work in an
embedded setting
> (the plugin) with out a front end of some sort.
>
> Any way, it's strange.  Hxplay runs in any directory
where all codecs
> are present (with full functionality), plays audio
regardless and will
> play audio in an embedded setting.  

> All of this is when using the
> hxplay script in debug, hxplay won't run at all in
> /player/installer/archive/temp currently.
>   

You meant hxplay script runs fine in:
  project.src_root_path/debug/
directory, but not in:
  project.src_root_path/player/installer/archive/temp?


-- 
Daniel Yek.


>  --
> Sarah Cooley
>
>
> On 8/13/07, Daniel Yek <dyekreal.com> wrote:
>   
>> The player works without installation if you
execute the realplay 
>> script at:
>>   player/installer/archive/temp/
>>
>>     

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

  
Re: Creating a player binary package
country flaguser name
United States
2007-08-16 18:36:00
Sarah Cooley wrote:
> Ok, so I got /player/installer/archive working (it
wasn't before) but
> am still running into problems.
>
> First, hopefully this isn't a big discrepancy,
cayenne_1_5_0 builds
> /client/core/clntcore.so, atlas_3_1_0 (our new branch)
builds
> hxmedplyeng.so instead of clntcore.so.  I modified the
make_tempdir to
> account for this but hxplay won't run in
player/installer/archive so I
> was thinking maybe that has a hand in it.
> Any idea what the differences are between the two?
>
> The error I'm getting is:
>
> cooleysXanadu:~/helix/gecko_plugin/player/installer/archive/
temp$ ./hxplay
>
> ** (hxplay.bin:16468): WARNING **: HXPlayer: Error
0x80004005: "A
> general error has occurred."
>
> ** (hxplay.bin:16468): WARNING **: Could not create
helix engine. Make
> sure your helix libs are installed at:
>
HELIX_LIBS=/home/cooleys/helix/gecko_plugin/player/installer
/archive/temp
>   

Does the following run?
cd
/home/cooleys/helix/gecko_plugin/player/installer/archive/te
mp
HELIX_LIBS=.  ./hxplay

(Note the dot following equal sign.)

> As far as video, I can't use the structure currently
set up on the
> OLPC because the GUI front end was written in python
ontop of splay
> and atlas which, as far as I know, won't work in an
embedded setting
> (the plugin) with out a front end of some sort.
>
> Any way, it's strange.  Hxplay runs in any directory
where all codecs
> are present (with full functionality), plays audio
regardless and will
> play audio in an embedded setting.  

> All of this is when using the
> hxplay script in debug, hxplay won't run at all in
> /player/installer/archive/temp currently.
>   

You meant hxplay script runs fine in:
  project.src_root_path/debug/
directory, but not in:
  project.src_root_path/player/installer/archive/temp?


-- 
Daniel Yek.


>  --
> Sarah Cooley
>
>
> On 8/13/07, Daniel Yek <dyekreal.com> wrote:
>   
>> The player works without installation if you
execute the realplay 
>> script at:
>>   player/installer/archive/temp/
>>
>>     

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

  
[1-7]

about | contact  Other archives ( Real Estate discussion Medical topics )