Are you using SYSTEM_ID of linux-2.2-libc6-gcc32-i586 for your builds on 
gcc3.2?
Which profile did you build?
Which target?
Does splay work with core you built?
Are you building with binary distributions or RA/RV codecs or from source?

vidrend is linked into various rendering plugins (e.g. 
datatype/rm/video/renderer).
Thus, those plugins would need to be rebuilt and plugins replaced for 
change to take effect.

Milko

At 08:35 PM 7/9/03 +0000, David Bear wrote:
>ok ,
>
>I managed to build vidrend by setting the target in build to 58  and it 
>appears to have 'built' my code.
>
>it built vidrend.a
>
>Do I need to now rebuild client core inorder to get my updates into the so 
>file?
>
>if not, how do I do it so that at runtime my vidrend.a file is loaded?
>
>additionally I still have the runtime error previously mentioned:
>
>https://helix-client.helixcommunity.org/servlets/ReadMsg?list=dev&msgNo=768
>
>What are the workarounds to these problems?
>
>David
>
>_________________________________________________________________
>STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org
>For additional commands, e-mail: dev-help at helix-client.helixcommunity.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org
For additional commands, e-mail: dev-help at helix-client.helixcommunity.org