List Info

Thread: how to build mjpeg and avi from helix cvs
how to build mjpeg and avi from helix cvs
user name
 2007-08-23 01:52:33 

  


  

    





        
I tried to get mjpeg and avi datatype from cvs as setting below, and got some
questions.



1.        
for mjpeg



 [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)



[1] Set Target(s)

(datatype_mjpeg)



[2] Set Profile
(/home/zhuao/helix_cvs/build/umakepf/helix-client-all-defines)



 



There was error in the
attached file mjpeg-error.log, I can’t get the code from cvs.




 



2.        
for avi



[0] Set BIF
branch (hxclient_1_5_0_cayenne_restricted)




[1] Set
Target(s) (datatype_avi_fileformat)



[2] Set Profile
(helix-client-all-defines)




 



When I run the
build, only static library “*.a” got, no dynamic library
“*.so” for plugin



 



Could you help
me on this?



Thanks.



 



 






ZHAO,
Halley (Aihua)



Email: halley.zhaointel.com" title="mailto:hui.xueintel.com">intel.com



Tel: +86(21)61166476



iNet: 8821-6476



SSG/OTC/UMD







 






  

  
  
   
     
    
 
        
    

    
    

  

    RE:  how to build mjpeg and avi from
helix cvs
  


  

     country flaguser name
United States		
     2007-08-23 07:36:38
  


  

    
Halley,

Regarding the mjpeg issue:

1) Both the "datatype_mjpeg" and the
"datatype_mjpeg_renderer" targets
   are listed in the hxclient_1_5_0_cayenne.bif as win32
only:

        <!-- DATATYPE/MJPEG/RENDERER  -->
        <module id="datatype_mjpeg_renderer"
name="datatype/mjpeg/renderer"
group="core">    
    	  <cvs root="helix"/>
          <attribute
id="has_version_file"/>
    
          <includeplatforms>
            win32 
          </includeplatforms>
    
          <dependlist>
             common_include
             common_runtime
             common_dbgtool
             common_container
             common_system
             common_util
             common_log_logutil
             client_include
             video_vidutil
             datatype_common_vidrend
             datatype_common_util
             datatype_common_container
    	 datatype_image_jpg_common
             datatype_image_jpg_import_jpeg-6b
          </dependlist>
        </module>

   Notice that only "win32" is listed in the
<includeplatforms> tag.
   However, I see no reason why anything in
datatype_mjpeg_renderer should
   not be cross-platform. So try adding "unix" to
the <includeplatforms>
   for both the "datatype_mjpeg" and
"datatype_mjpeg_renderer" targets
   and rebuild.

2. Regarding datatype/avi/fileformat, this target is
normally built
   as a static lib and then packaged into the
datatype/video/group
   binary. Therefore, try building datatype_video_group in
   the same BIF file. The resulting vidplin.so should
contain
   datatype/avi/fileformat.

Hope this helps.

Eric

=============================================
Eric Hyche (ehychereal.com)
Technical Lead
RealNetworks, Inc.  

> -----Original Message-----
> From: helix-client-dev-bounceshelixcommunity.org 
> [mailto:helix-client-dev-bounceshelixcommunity.org] On 
> Behalf Of Zhao, Halley
> Sent: Thursday, August 23, 2007 2:53 AM
> To: helix-client-devhelixcommunity.org
> Subject: [Helix-client-dev] how to build mjpeg and avi
from helix cvs
> 
>          I tried to get mjpeg and avi datatype from cvs
as 
> setting below, and got some questions.
> 
> 1.         for mjpeg
> 
>  [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)
> 
> [1] Set Target(s) (datatype_mjpeg)
> 
> [2] Set Profile 
>
(/home/zhuao/helix_cvs/build/umakepf/helix-client-all-define
s)
> 
>  
> 
> There was error in the attached file mjpeg-error.log, I
can't 
> get the code from cvs.
> 
>  
> 
> 2.         for avi
> 
> [0] Set BIF branch (hxclient_1_5_0_cayenne_restricted)
> 
> [1] Set Target(s) (datatype_avi_fileformat)
> 
> [2] Set Profile (helix-client-all-defines)
> 
>  
> 
> When I run the build, only static library
"*.a" got, no 
> dynamic library "*.so" for plugin
> 
>  
> 
> Could you help me on this?
> 
> Thanks.
> 
>  
> 
>  
> 
> ZHAO, Halley (Aihua)
> 
> Email: halley.zhaointel.com <mailto:aihua.zhaointel.com> 
> 
> Tel: +86(21)61166476
> 
> iNet: 8821-6476
> 
> SSG/OTC/UMD
> 
>  
> 
> 


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev



  


  

    
  

  
  
   
     
    

  

    RE:  how to build mjpeg and avi from
helix cvs
  


  

     user name

     2007-08-24 02:47:50
  


  

    
　　Thanks Eric.
　　Follow your instruction, I got some progress:
　　1 . mjpeg
　　		Update in hxclient_1_5_0_cayenne.bif
　　		a) Add unix for includeplatforms:
　　			<includeplatforms>
　　            unix win32
　　          </includeplatforms>
　　		b)  Add protocol_common_util and protocol_sdp in
depend list for datattype_mjpeg_render:
　　       see datatype_mjpeg_renderer.txt
　　		c) then I can pass the build of mjpeg plugin. But
there is still a bug that the video is upside down; the
bottom line is at the top, and the top line is at the
bottom.
　　     d) Could anyone update the ribosome, then I can
submit a patch to fix the bug of video upside down.
　　2.  avi
　　	  a) When I build the target datatype_video_group,
there is still no avi fileformat plugin. And
datatype_video_group is a render group for rv, mp4, h263
etal. No fileforamt plugin included.
　　  b) in datatype/avi/fileformat/ there is Umakefil, I
update it to generate  "aviffformat.so"
　　if project.IsDefined("HELIX_FEATURE_SERVER"):
　　   
MultiTargetMake("aviffdll","avifflib")
　　else:
　　   
MultiTargetMake("aviffdll","avifflib")
　　c) I also add common_log_logutil module in depend list
of hxclient_1_5_0_cayenne.bif
　　see datatype_avi_fileformat.txt
　　d)   we should also update the root Umakefil for avi
fileformat target to let the ribosome check out
common/log/util module like following
　　project.AddSubModule('common/log/logutil/Umakefil',
'common/log/logutil/Makefile')
　　	e) Finally, I can generate avifformat.so; however,
there is still error when I use this plugin,
"Unsupported document type. (The stream URL is not a
valid AVI)".  I think I can look into the issue.
　　
　　		
　　>-----Original Message-----
　　>From: Eric Hyche [mailto:ehychereal.com]
　　>Sent: 2007定8埖23晩 20:37
　　>To: Zhao, Halley; helix-client-devhelixcommunity.org
　　>Subject: RE: [Helix-client-dev] how to build mjpeg
and avi from helix cvs
　　>
　　>
　　>Halley,
　　>
　　>Regarding the mjpeg issue:
　　>
　　>1) Both the "datatype_mjpeg" and the
"datatype_mjpeg_renderer" targets
　　>   are listed in the hxclient_1_5_0_cayenne.bif as
win32 only:
　　>
　　>        <!-- DATATYPE/MJPEG/RENDERER  -->
　　>        <module
id="datatype_mjpeg_renderer"
　　>name="datatype/mjpeg/renderer"
group="core">
　　>    	  <cvs root="helix"/>
　　>          <attribute
id="has_version_file"/>
　　>
　　>          <includeplatforms>
　　>            win32
　　>          </includeplatforms>
　　>
　　>          <dependlist>
　　>             common_include
　　>             common_runtime
　　>             common_dbgtool
　　>             common_container
　　>             common_system
　　>             common_util
　　>             common_log_logutil
　　>             client_include
　　>             video_vidutil
　　>             datatype_common_vidrend
　　>             datatype_common_util
　　>             datatype_common_container
　　>    	 datatype_image_jpg_common
　　>             datatype_image_jpg_import_jpeg-6b
　　>          </dependlist>
　　>        </module>
　　>
　　>   Notice that only "win32" is listed in
the <includeplatforms> tag.
　　>   However, I see no reason why anything in
datatype_mjpeg_renderer should
　　>   not be cross-platform. So try adding
"unix" to the <includeplatforms>
　　>   for both the "datatype_mjpeg" and
"datatype_mjpeg_renderer" targets
　　>   and rebuild.
　　>
　　>2. Regarding datatype/avi/fileformat, this target is
normally built
　　>   as a static lib and then packaged into the
datatype/video/group
　　>   binary. Therefore, try building
datatype_video_group in
　　>   the same BIF file. The resulting vidplin.so
should contain
　　>   datatype/avi/fileformat.
　　>
　　>Hope this helps.
　　>
　　>Eric
　　>
　　>=============================================
　　>Eric Hyche (ehychereal.com)
　　>Technical Lead
　　>RealNetworks, Inc.
　　>
　　>> -----Original Message-----
　　>> From: helix-client-dev-bounceshelixcommunity.org
　　>> [mailto:helix-client-dev-bounceshelixcommunity.org] On
　　>> Behalf Of Zhao, Halley
　　>> Sent: Thursday, August 23, 2007 2:53 AM
　　>> To: helix-client-devhelixcommunity.org
　　>> Subject: [Helix-client-dev] how to build mjpeg
and avi from helix cvs
　　>>
　　>>          I tried to get mjpeg and avi datatype
from cvs as
　　>> setting below, and got some questions.
　　>>
　　>> 1.         for mjpeg
　　>>
　　>>  [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)
　　>>
　　>> [1] Set Target(s) (datatype_mjpeg)
　　>>
　　>> [2] Set Profile
　　>>
(/home/zhuao/helix_cvs/build/umakepf/helix-client-all-define
s)
　　>>
　　>>
　　>>
　　>> There was error in the attached file
mjpeg-error.log, I can't
　　>> get the code from cvs.
　　>>
　　>>
　　>>
　　>> 2.         for avi
　　>>
　　>> [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)
　　>>
　　>> [1] Set Target(s) (datatype_avi_fileformat)
　　>>
　　>> [2] Set Profile (helix-client-all-defines)
　　>>
　　>>
　　>>
　　>> When I run the build, only static library
"*.a" got, no
　　>> dynamic library "*.so" for plugin
　　>>
　　>>
　　>>
　　>> Could you help me on this?
　　>>
　　>> Thanks.
　　>>
　　>>
　　>>
　　>>
　　>>
　　>> ZHAO, Halley (Aihua)
　　>>
　　>> Email: halley.zhaointel.com
<mailto:aihua.zhaointel.com>
　　>>
　　>> Tel: +86(21)61166476
　　>>
　　>> iNet: 8821-6476
　　>>
　　>> SSG/OTC/UMD
　　>>
　　>>
　　>>
　　>>

_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev



  


  

    
  

  
  
   
     
    
 
        
    

    
    
 
        
    

    
    
 
        
    

    
    

  

    RE:  how to build mjpeg and avi from
helix cvs
  


  

     country flaguser name
United States		
     2007-08-24 08:14:24
  


  

    

> -----Original Message-----
> From: Zhao, Halley [mailto:halley.zhaointel.com] 
> Sent: Friday, August 24, 2007 3:48 AM
> To: ehychereal.com; helix-client-devhelixcommunity.org
> Cc: Shen, Cathy; Wei, Donald; Zhao, Halley
> Subject: RE: [Helix-client-dev] how to build mjpeg and
avi 
> from helix cvs
> 
> $B!!!!(BThanks Eric.
> $B!!!!(BFollow your instruction, I got some
progress:
> $B!!!!(B1 . mjpeg
> $B!!!!(B		Update in hxclient_1_5_0_cayenne.bif
> $B!!!!(B		a) Add unix for includeplatforms:
> $B!!!!(B			<includeplatforms>
> $B!!!!(B            unix win32
> $B!!!!(B          </includeplatforms>
> $B!!!!(B		b)  Add protocol_common_util and
protocol_sdp 
> in depend list for datattype_mjpeg_render:
> $B!!!!(B       see datatype_mjpeg_renderer.txt
> $B!!!!(B		c) then I can pass the build of mjpeg
plugin. 
> But there is still a bug that the video is upside down;
the 
> bottom line is at the top, and the top line is at the
bottom.
> $B!!!!(B     d) Could anyone update the ribosome,
then I can submit 
> a patch to fix the bug of video upside down.

You can just submit that patch for changing the BIF along
with
the change for fixing the upside-down video.

> $B!!!!(B2.  avi
> $B!!!!(B	  a) When I build the target
datatype_video_group, 
> there is still no avi fileformat plugin. And 
> datatype_video_group is a render group for rv, mp4,
h263 
> etal. No fileforamt plugin included.
> $B!!!!(B  b) in datatype/avi/fileformat/ there is
Umakefil, I 
> update it to generate  "aviffformat.so"
> $B!!!!(Bif
project.IsDefined("HELIX_FEATURE_SERVER"):
> $B!!!!(B   
MultiTargetMake("aviffdll","avifflib")
> $B!!!!(Belse:
> $B!!!!(B   
MultiTargetMake("aviffdll","avifflib")
> $B!!!!(Bc) I also add common_log_logutil module in
depend list of 
> hxclient_1_5_0_cayenne.bif
> $B!!!!(Bsee datatype_avi_fileformat.txt
> $B!!!!(Bd)   we should also update the root Umakefil
for avi 
> fileformat target to let the ribosome check out 
> common/log/util module like following
>
$B!!!!(Bproject.AddSubModule('common/log/logutil/Umakefil'
, 
> 'common/log/logutil/Makefile')
> $B!!!!(B	e) Finally, I can generate avifformat.so;
however, 
> there is still error when I use this plugin,
"Unsupported 
> document type. (The stream URL is not a valid
AVI)".  I think 
> I can look into the issue.
> $B!!!!(B

Probably the easiest way to change the Umakefil is just
to make the dll all the time:

- if project.IsDefined("HELIX_FEATURE_SERVER"):
    MultiTargetMake("aviffdll")
- else:
-     MultiTargetMake("avifflib")


Eric
=============================================
Eric Hyche (ehychereal.com)
Technical Lead
RealNetworks, Inc. 
> $B!!!!(B		
> $B!!!!(B>-----Original Message-----
> $B!!!!(B>From: Eric Hyche [mailto:ehychereal.com]
> $B!!!!(B>Sent: 2007$BG/(B8$B7n(B23$BF|(B
20:37
> $B!!!!(B>To: Zhao, Halley; helix-client-devhelixcommunity.org
> $B!!!!(B>Subject: RE: [Helix-client-dev] how to
build mjpeg and avi 
> from helix cvs
> $B!!!!(B>
> $B!!!!(B>
> $B!!!!(B>Halley,
> $B!!!!(B>
> $B!!!!(B>Regarding the mjpeg issue:
> $B!!!!(B>
> $B!!!!(B>1) Both the "datatype_mjpeg"
and the 
> "datatype_mjpeg_renderer" targets
> $B!!!!(B>   are listed in the
hxclient_1_5_0_cayenne.bif as win32 only:
> $B!!!!(B>
> $B!!!!(B>        <!-- DATATYPE/MJPEG/RENDERER 
-->
> $B!!!!(B>        <module
id="datatype_mjpeg_renderer"
> $B!!!!(B>name="datatype/mjpeg/renderer"
group="core">
> $B!!!!(B>    	  <cvs
root="helix"/>
> $B!!!!(B>          <attribute
id="has_version_file"/>
> $B!!!!(B>
> $B!!!!(B>          <includeplatforms>
> $B!!!!(B>            win32
> $B!!!!(B>          </includeplatforms>
> $B!!!!(B>
> $B!!!!(B>          <dependlist>
> $B!!!!(B>             common_include
> $B!!!!(B>             common_runtime
> $B!!!!(B>             common_dbgtool
> $B!!!!(B>             common_container
> $B!!!!(B>             common_system
> $B!!!!(B>             common_util
> $B!!!!(B>             common_log_logutil
> $B!!!!(B>             client_include
> $B!!!!(B>             video_vidutil
> $B!!!!(B>             datatype_common_vidrend
> $B!!!!(B>             datatype_common_util
> $B!!!!(B>             datatype_common_container
> $B!!!!(B>    	 datatype_image_jpg_common
> $B!!!!(B>            
datatype_image_jpg_import_jpeg-6b
> $B!!!!(B>          </dependlist>
> $B!!!!(B>        </module>
> $B!!!!(B>
> $B!!!!(B>   Notice that only "win32" is
listed in the 
> <includeplatforms> tag.
> $B!!!!(B>   However, I see no reason why anything
in 
> datatype_mjpeg_renderer should
> $B!!!!(B>   not be cross-platform. So try adding
"unix" to the 
> <includeplatforms>
> $B!!!!(B>   for both the
"datatype_mjpeg" and 
> "datatype_mjpeg_renderer" targets
> $B!!!!(B>   and rebuild.
> $B!!!!(B>
> $B!!!!(B>2. Regarding datatype/avi/fileformat,
this target is normally built
> $B!!!!(B>   as a static lib and then packaged into
the datatype/video/group
> $B!!!!(B>   binary. Therefore, try building
datatype_video_group in
> $B!!!!(B>   the same BIF file. The resulting
vidplin.so should contain
> $B!!!!(B>   datatype/avi/fileformat.
> $B!!!!(B>
> $B!!!!(B>Hope this helps.
> $B!!!!(B>
> $B!!!!(B>Eric
> $B!!!!(B>
>
$B!!!!(B>=============================================
> $B!!!!(B>Eric Hyche (ehychereal.com)
> $B!!!!(B>Technical Lead
> $B!!!!(B>RealNetworks, Inc.
> $B!!!!(B>
> $B!!!!(B>> -----Original Message-----
> $B!!!!(B>> From: helix-client-dev-bounceshelixcommunity.org
> $B!!!!(B>> [mailto:helix-client-dev-bounceshelixcommunity.org] On
> $B!!!!(B>> Behalf Of Zhao, Halley
> $B!!!!(B>> Sent: Thursday, August 23, 2007 2:53
AM
> $B!!!!(B>> To: helix-client-devhelixcommunity.org
> $B!!!!(B>> Subject: [Helix-client-dev] how to
build mjpeg and avi 
> from helix cvs
> $B!!!!(B>>
> $B!!!!(B>>          I tried to get mjpeg and
avi datatype from cvs as
> $B!!!!(B>> setting below, and got some
questions.
> $B!!!!(B>>
> $B!!!!(B>> 1.         for mjpeg
> $B!!!!(B>>
> $B!!!!(B>>  [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)
> $B!!!!(B>>
> $B!!!!(B>> [1] Set Target(s) (datatype_mjpeg)
> $B!!!!(B>>
> $B!!!!(B>> [2] Set Profile
> $B!!!!(B>>
(/home/zhuao/helix_cvs/build/umakepf/helix-client-all-define
s)
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>> There was error in the attached file
mjpeg-error.log, I can't
> $B!!!!(B>> get the code from cvs.
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>> 2.         for avi
> $B!!!!(B>>
> $B!!!!(B>> [0] Set BIF branch
(hxclient_1_5_0_cayenne_restricted)
> $B!!!!(B>>
> $B!!!!(B>> [1] Set Target(s)
(datatype_avi_fileformat)
> $B!!!!(B>>
> $B!!!!(B>> [2] Set Profile
(helix-client-all-defines)
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>> When I run the build, only static
library "*.a" got, no
> $B!!!!(B>> dynamic library "*.so" for
plugin
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>> Could you help me on this?
> $B!!!!(B>>
> $B!!!!(B>> Thanks.
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>> ZHAO, Halley (Aihua)
> $B!!!!(B>>
> $B!!!!(B>> Email: halley.zhaointel.com
<mailto:aihua.zhaointel.com>
> $B!!!!(B>>
> $B!!!!(B>> Tel: +86(21)61166476
> $B!!!!(B>>
> $B!!!!(B>> iNet: 8821-6476
> $B!!!!(B>>
> $B!!!!(B>> SSG/OTC/UMD
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> $B!!!!(B>>
> 


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev



  


  

    
  

  
  
   
     
    






 [1-4]











   
 





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