-----Original Message-----
From: [email protected]
[mailto:[email protected]
] On Behalf Of Griffis, Brad
Sent: Monday, February 09, 2009 10:06 PM
To: Ryan Talbot; [email protected]
Subject: RE: Dsplink.dsp?
This path is likely incorrect:
/home/rtalbot/dvevm_2_21/dsplink_1_60/packages
You need to do one of the following to fix it:
1) Root through the various makefiles to figure out where
they define XDCPATH and delete the extra "packages" they are
appending to the dsplink path.
- OR -
2) Add a "packages" folder in between the "dsplink_1_60"
folder and the "dsplink" folder. (This is probably the
quickest/easiest.)
I think this all came about because there is a CONVENTION at
TI to put all the RTSC packages of a product into a directory
called "packages". DSPLink does not follow this convention
and the DVSDK tried to force the convention upon DSPLink. So
in the version of dsplink that is delivered with the DVSDK
they created that extra directory called "packages" so it
would follow the same convention as everything else. It
makes everything look uniform, but it can be a real pain in
the rear if you try to use a freshly downloaded version of dsplink.
Brad
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On
Behalf Of Ryan Talbot
Sent: Saturday, February 07, 2009 2:01 AM
To: [email protected]
Subject: Dsplink.dsp?
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/
rtalb
ot
/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_com
po
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
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
source
