Hi Ryan,
Just write the simplest config.bld to define the compiler and target
like this:
var C64P = xdc.useModule('ti.targets.C64P');
C64P.rootDir="/home/armdsp/dvsdk_1_40_02_33/cg6x_6_0_21";
C64P.platform = "ti.platforms.evmDM6446";
Build.targets = [
C64P,
];
Then set XDCPATH like below:
#!/bin/sh
DVSDK_INSTALL_DIR=${HOME}/dvsdk
BIOS_INSTALL_DIR=${DVSDK_INSTALL_DIR}/bios_5_33_03
CEUTILS_INSTALL_DIR=${DVSDK_INSTALL_DIR}/ceutils_1_06
XDC_INSTALL_DIR=${DVSDK_INSTALL_DIR}/xdc_3_10_03
CE_INSTALL_DIR=${DVSDK_INSTALL_DIR}/codec_engine_2_21
LINK_INSTALL_DIR=${DVSDK_INSTALL_DIR}/dsplink_1_60
FC_INSTALL_DIR=${DVSDK_INSTALL_DIR}/framework_components_2_21
XDAIS_INSTALL_DIR=${DVSDK_INSTALL_DIR}/xdais_6_21
CMEM_INSTALL_DIR=${DVSDK_INSTALL_DIR}/linuxutils_2_21
CODECS_INSTALL_DIR=${DVSDK_INSTALL_DIR}/dm6446_codecs_2_0
BIOSUTILS_INSTALL_DIR=${DVSDK_INSTALL_DIR}/biosutils_1_01_02
#Setlocationofxdcexecutable
XDC=${XDC_INSTALL_DIR}/xdc
XS=${XDC_INSTALL_DIR}/xs
#SetXDCPATHtocontainnecessaryrepositories.
XDCPATH="${CEUTILS_INSTALL_DIR}/packages;${CODECS_INSTALL_DIR}/
packages-evaluation;${XDAIS_INSTALL_DIR}/packages;${FC_INSTALL_DIR}/
packages;${FC_INSTALL_DIR}/fctools/packages;${BIOS_INSTALL_DIR}/
packages;${CMEM_INSTALL_DIR}/packages;${LINK_INSTALL_DIR}/packages;$
{CE_INSTALL_DIR}/packages;${BIOSUTILS_INSTALL_DIR}/packages"
export XDC
export XDCPATH
export XS
Then compile your server like this:
$XDC -PD .
I don't know that what you are compiling for, DM644x or DM357.
Buf if you are compiling for DM644x, and unfortunately you are using
codecs from TI version earlier than 2.0, you will find that video_copy
is ok to run, bun codecs, no!
Good luck if you have got the DVSDK_2.0_EA. And please drop me a
message.
Yours David Chan ( also known as blacksword.david)
Message: 6
Date: Sat, 7 Feb 2009 03:00:36 -0500
From: "Ryan Talbot" <[email protected]>
Subject: Dsplink.dsp?
To: <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi folks,
I feel that I must have missed something simple, but I can't for the
life of me figure out what it was. I followed the directions to build
the DSP side of DSPLink that are outlined here:
http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink
...including the instructions for the XDC integration.
I received no errors on build. However, when I got to building a 3rd
party server, I get the following error:
js:
"/home/rtalbot/dvevm_2_21/xdctools_3_10_03/packages/xdc/cfg/Main.xs",
line 201: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND:
can't
locate the package 'dsplink.dsp' along the path:
'/home/rtalbot/dvevm_2_21;/home/rtalbot/dvevm_2_21/
codec_servers_1_23/pa
ckages;/home/rtalbot/dvevm_2_21/codec_engine_2_21/packages;/home/
rtalbot
/dvevm_2_21/dsplink_1_60/packages;/home/rtalbot/dvevm_2_21/
xdais_6_21/pa
ckages;/home/rtalbot/dvevm_2_21/linuxutils_2_21/packages;/home/
rtalbot/d
vevm_2_21/bios_5_33_02/packages;/home/rtalbot/dvevm_2_21/
framework_compo
nents_2_21/packages;/home/rtalbot/dvevm_2_21/xdctools_3_10_03/
packages;.
./../..;'. Ensure that the package path is set correctly.
I called the base directory 'dvevm_2_21' for lack of any better name
for
the hodge-podge of components that works with CodecEngine 2.21. These
paths are all correct (at least, they all exist). The codec build
went
fine, but this, the server build, is failing.
I could build this 3rd party bundle (codec, server, and example
program)
just fine using dvevm_1_20 (codec_engine_1_10_01 and friends).
There is
no actual file called dsplink.dsp in either version.
I wonder if this has to do with the 'config.bld' file in my
'codec_engine_2_21/packages' directory? There wasn't one included
like
there was with the monolithic DVEVM/DVSDK releases, and it was causing
the 3rd party builds to do absolutely nothing. I copied the one out
of
the codec_engine_2_00_01/packages directory that came with
DVSDK-1.30.01.41, which got my codec build working. Also, I built
DSPLink in its own directory (dsplink_1_60 in the above paths), not
within the cetools directory of CodecEngine... could that be the
problem?
Any help appreciated. This build system (actually, TI's hierarchy of
software in general) confuses the heck out of me.
Ryan Talbot
[email protected]
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 38, Issue 35
*********************************************************
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
