Error "can't locate the package 'ti.sdo.ce.osal' along the path"

Ofer Zimmerman

Hi,

I am trying to build a iUniversial type application. I successfully generated and packaged my own CODEC (via the CODEC package generation Wizard) and a server (via the server package generation Wizard). Next I created an application (reused the code and structure of randgen from the iUNIVERSAL examples as suggested by the documentation). I hit the same issue with my own application and also with the iUNIVERSIAL examples' applications: randgen and fir in which packages under the code engine directories are not found. I guess the problem is path issue and indeed the -Dxdc_path printed on the Linux monitor states the XDC install directory only (in addition to /../../ etc). I did set in the Makefile the XDCPATH to include also code_engine/packages and code_engine/cetools and other directories but still it did not help.

Thanks Ofer

over 14 years ago

0 Chris Ring over 14 years ago

TI__Genius 17205 points

Can you post your build log? Might help us see how you're build flow looks and what setting is missing.

Note that it's codec_engine, not code_engine - maybe just a typo in your post, but if it's a typo in your makefile, that could be a bigger issue. :)

Chris

0 Ofer Zimmerman over 14 years ago in reply to Chris Ring

Intellectual 995 points

2671.config_bld.txthttp://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/356/2845.c[View:http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/356/3426.Makefile_5F00_app.txtonfig.txt]Hi,

yes I know it is codec (it is only a typo) and actually my makefile points to the exact codec install directory. Before providing the log I would like to present the XDCPATH settings of mine: in the Makefile I have XDCPATH=/home/ofer62/xdctools_3_16_00_18/packages;/home/ofer62/codec_engine_2_26_02_11/packages;/home/ofer62/codec_engine_2_26_02_11/cetools/packages and more installed directories (DSP link, BIOS etc) and then I have later export XDCPATH (which I changed to "XDCPATH" or else nothing is working). then in the Makefile.app I have $(PRE) XDCPATH=$(XDCPATH) $(CONFIGURO) -o $(XDC_CFG) -t $(XDC_ARM_TARGET) -p and more

I attached the build log and also my Makefile and Makefile.app and config.bld

Thanks Ofer0118.Makefile.txt

3821.Build.log

0 Chris Ring over 14 years ago in reply to Ofer Zimmerman

TI__Genius 17205 points

Env vars can be tricky in make and different shells. Instead, I tend to use the --xdcpath argument to the 'xs' executable used to launch configuro.

http://rtsc.eclipse.org/docs-tip/Command_-_xs

Maybe you can try something like this in your makefile?

xs --xdcpath $(XDCPATH) xdc.tools.configuro ...

Chris

0 Ofer Zimmerman over 14 years ago in reply to Chris Ring

Intellectual 995 points

I will try this also I quite sure that I already did something similar (since this is the method successfuly used in my Server and Coded projects) that big question how to make the -Dxdc.path be all the directories that are listed under XDCPATH, as you can see in the build.log only the XDC tools dir is set which is probably the default of the tool

Thanks Ofer

0 Ofer Zimmerman over 14 years ago in reply to Ofer Zimmerman

Intellectual 995 points

By the way there is no --xdcpath argument for xs, but for xdc ?

0 Ofer Zimmerman over 14 years ago in reply to Ofer Zimmerman

Intellectual 995 points

Hi,

OK now I can compile (XDCPATH is OK). But now it fails with "collect2: ld terminated with signal 11 segmentation fault

Ofer

Processors

Processors forum

Error "can't locate the package 'ti.sdo.ce.osal' along the path"