• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 613 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

XDC seems to be loading the wrong config.bld file

HyperGalaxy
Intellectual 670 points

I am trying to build a simple codec server, and my runxdc.sh file looks like this:

 

#! /bin/sh

#  import install paths
. ../setpaths.sh

#  Define search paths for included packages
export XDCPATH="$CE_INSTALL_DIR/examples;$CE_INSTALL_DIR/packages;$XDAIS_INSTALL_DIR/packages;$DSPLINK_INSTALL_DIR/packages;$CMEM_INSTALL_DIR/packages;$FC_INSTALL_DIR/packages;$XDC_INSTALL_DIR/packages;$BIOS_INSTALL_DIR/packages;$DVEVM_INSTALL_DIR/biosutils_1_00_02/packages"

#  Define options for execution
export XDCBUILDCFG="$(pwd)/../config.bld"

echo "XDCBUILDCFG = $XDCBUILDCFG"

export XDCOPTIONS="-v"   ###  display each command before it is executed

#  Execute xdc command
xdc $@ -P *

 

My XDCBUILDCFG environment variable is set to /home/darwin/projects/LightSpeed/tests/soln12a_build_server/../config.bld by this file. However, XDC specifies /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/config.bld on the command line, instead. Why am I observing this behavior?

 

BTW, I added the following code to the package.bld file in my app and server directories, which got around the problem, but it would be good to understand why XDC is ignoring my XDCBUILDCFG environment variable:


if ( undefined == paths )
{
   var paths = [] ;
   paths["EXEC_DIR"] = java.lang.System.getenv( "EXEC_DIR" ) ;
}
print( 'paths["EXEC_DIR"]=' + paths["EXEC_DIR"] ) ;

Any help would be greatly appreciated.

 

Have a great day!

 

Take care,

Darwin

  • 0
    TI__Guru*** 125430 points

    I'm not sure if this will help you or not, but you might want to try adding "XDCBUILDCFG=$XDCBUILDCFG" to the command line.  The XDC tools are built on top of make.  In make, a variable set on the command line will override variables in the makefile whereas an environment variable will not.  For that reason I suspect it might help.  Let us know. 

    Also, the BEST place for help related to XDCtools is at http://rtsc.eclipse.org.  They've setup a newsgroup over there.  We will help you as much as we can here, but the actual developers of XDCtools are monitoring the newsgroup rather than these forums.  (I know it seems kind of strange, but due to the fact that they've been picked up as an Eclipse-related project they are supposed to keep as much info as possible out in the open on that Eclipse web site.)