|
Even after changing the name to
realformat_sdk_include, we are getting the same error.
Target used:
<!-- INCLUDE
-->
; <module
id="realformat_sdk_include" name="realformat-sdk/include"
group="core">
;
<cvs
branch="HEAD"/>
;
<cvs
path="realformat-sdk/include"/>
;
<attribute id="no_build"/>
</module>
--Jinu
Try to change the name of the target only to realformat_sdk_include
(using underscore instead of hyphen).
-Rishi.
At 12:54 AM 3/28/2007, Jinu Thomas wrote:
There are no issues in
checking out into (and thus naming to)
"realformat-sdk/include"(name="realformat-sdk/include") instead of just
"include". The code will check out into realformat-sdk/include folder and builds
fine. But naming the new target to
realformat-sdk_include(id="realformat-sdk_include") is giving some error while
checking out the code. The error is mentioned below. How shall I proceed? Pls
advise
[#-00000118][2007-03-28 12:07:01][2832][INFO ] : Building
dependency tree for targets.
[#-00000119][2007-03-28 12:07:01][2832][ERROR] :
--- Build System Error ------------------------------------
You have found a
Ribosome
bug.
-----------------------------------------------------------
---
Python Traceback
--------------------------------------
------------------------------------
Traceback
(most recent call last):
File "c:sourcebuildbinlauncher.py", line
117, in __runTool
; tool.run()
File
"C:sourcebuildlibbuild_exe.py", line 896, in run
;
ShellToolApp().main()
File "C:sourcebuildlibbuild_exe.py", line
470, in main
; apply(self.menu[i][1],
self.menu[i][2:])
File "C:sourcebuildlibbuild_exe.py", line 693,
in CheckoutSource
; self.build(self.flags +
["-h"])
File "C:sourcebuildlibbuild_exe.py", line 492, in
build
invoke_buildsystem(arg_list)
File
"C:sourcebuildlibbuild_exe.py", line 111, in
invoke_buildsystem
; app =
buildapp.RunBuild(arg_list)
File "C:sourcebuildlibbuildapp.py",
line 102, in RunBuild
app.main()
File
"C:sourcebuildlibbuildapp.py", line 196, in main
;
self.run()
File "C:sourcebuildlibbuildapp.py", line 375, in
run
self.setup_depends()
File
"C:sourcebuildlibbuildapp.py", line 556, in
setup_depends
; self.depends =
dependlist.DependList(bif_data, target_tmp)
File
"C:sourcebuildlibdependlist.py", line 271, in __init__
sdep_module = self.bif_data.module_hash[sourcedep]
KeyError:
'include'
-----------------------------------------------------------
--Jinu
;
At 09:33 AM 3/27/2007, Jinu Thomas wrote:
Modifications has been made as
per the review comments and the updated diff file is
attached.
Greg Wright <real.com">gwright real.com>
03/27/2007 10:18
PM
;
Jinu Thomas wrote:
>; As you have
mentioned I have copied that particular target from the realformat-sdk.bif and
copied it into hxclient_2_1_0_cayennes.bif. But I was unable to check -out that
particular target. It is giving some error .]
> The target
is:
> ; <!-- INCLUDE
-->
> <module id="include"
name="include"
group="core">
> ;
<cvs
path="realformat-sdk/include"/>
> ;
<attribute id="no_build"/>
>
</module>
>;
> The error I'm getting while checking-out:
>
> Moving
.datatype-restricted/rm/video/codec/rv89combo/platformcvstmpdir_2148tmp to
datatype-restricted/rm/video/codec/rv89combo/platform/emuzed
> checking
out [helix]include tag="hxclient_2_1_0_cayennes" from
path="realformat-sdk/include"
> running 'cvs -d
:ext:jinuthomascvs.helixcommunity.org:/cvsroot/realformat-sdk checkout -r
"hxclient_2_1_0_cayennes" -d tmp include' in 'c:\source\helix' +
'.\cvstmpdir_1304' (as = '.\cvstmpdir_1304\tmp')
> cvs [checkout
aborted]: no such tag hxclient_2_1_0_cayennes
> [#-00000421][2007-03-27
14:27:06][1304][INFO ] : CVS command failed with error code 1, trying again in a
few seconds.
> cvs [checkout aborted]: no such tag
hxclient_2_1_0_cayennes
> [#-00000424][2007-03-27 14:27:13][1304][INFO ] :
CVS command failed with error code 1, trying again in a few seconds.
> cvs
[checkout aborted]: no such tag hxclient_2_1_0_cayennes
>
[#-00000427][2007-03-27 14:27:26][1304][INFO ] : CVS command failed with error
code 1, trying again in a few seconds.
> cvs [checkout aborted]: no such
tag hxclient_2_1_0_cayennes
> [#-00000430][2007-03-27 14:27:44][1304][INFO
] : CVS command failed with error code 1, trying again in a few seconds.
>
cvs [checkout aborted]: no such tag hxclient_2_1_0_cayennes
>
[#-00000433][2007-03-27 14:28:06][1304][INFO ] : CVS command failed with error
code 1, trying again in a few seconds.
> cvs [checkout aborted]: no such
tag hxclient_2_1_0_cayennes
>
>
> I feel the only possible
way to do the same is to inherit the target from the realfromat-sdk. With this
modification code check-out and building works fine. Actually whoever wants to
build the target datatype-restricted_rm_video_codec_rv89combo_emuzed
should have the realformat-sdk code since it is using some files from
realformat-sdk code . The bif file hxclient_2_1_0_cayennes.bif from which it is
inherited also belongs to some other code space( Client). So how shall I
proceed? Please Advise.
I think the problem is that the
RealFormat SDK has not been branched to
210CayS. So, you need to add a branch
tag for that one target. Here is
one example of
how:
<module
id="producersdk_common_container" name="producersdk/common/container"
group="tools">
; <cvs
root="helix"/>
; <cvs
branch="producer_10"/>
<includeplatforms>
;
unix mac win32
</includeplatforms>
...
...
You could
just change the branch to 150Cay, HEAD or whatever. We could also branch
the
RealFormat SDK to 210CayS. It just depends on what you are after. Any
fixes
to the RF SDK will probably be made on HEAD and 150Cay, with 150Cay
being much
more stable. So, you would not have to worry about merging fixes
to 210CayS if
you picked up the SDK from
150Cay.
--greg.
>
>
>
--Jinu
>
>
>
>
>
>
>
>
Greg Wright < gwrightreal.com">gwrightreal.com>
> 03/27/2007 05:56 AM
>
> To
> Jinu Thomas
< jinuemuzed.com">jinuemuzed.com>
> cc
>
helixcommunity.org">datatype-devhelixcommunity.org,
helixcommunity.org">helix-client-devhelixcommunity.org
>
Subject
> Re: [datatype-dev] CR-RESEND: MDF Wrapper for the RV89
Combo Decoder
>
>
> ;
>
>
> +<inherit
id="[realformat-sdk]realformat-sdk"/>
> <inherit
id="[client]hxclient_2_1_0_cayennes"/>
>
>
> This seems a
bit strange, we normally only inherit from one
> BIF file, I am not sure
if this might cause problems for
> you (it may not). If you only need 1
target from that, it
> could just be cut-n-pasted in to the 210CayS. I am
not sure
> if including the realformat-sdk would also cause
anything
> strange to happen with code getting checked out on
multiple
> branches or something similar. What about folks that
don't
> have access to the realformat-sdk code, any problems
there?
>
>
> -1824,7 +1826,7
> ; ;
common_runtime
> ;
common_system <!-- only for multi-threading
-->
> & |