• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 363 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 Generated Makefile Problem

Nick Borton
Genius 3595 points

Hello,

I have a handful of custom XDC modules which use the twiddle generation C code from DSPLib. The package.bld file calls out the CM'ed location of the twiddle C file as an absolute path. In a Linux environment there is no issue with the absolute path. In windows on the other hand (which the majority of developers in my company run), the absolute path includes the driver letter designation (C:, D:, E:, etc.). The absolute path is used in the makefile rule generation by XDC. So the build process dies because the : designates a rule in make. Is there a way for absolute paths to work in XDC?

Thanks!

  • 0
    TI__Mastermind 37985 points

    Can you use vpath? That's how some core XDCtools packages that use sources from different directories are built. It seems that vpath works just fine with absolute paths on Windows. However, your case could be a little different because your sources are not in a RTSC package. You can insert a vpath directive into a generated makefile through the parameter makePrologue. 

    For example, if your sources are in C:/temp, you can add the following line to your package.bld:

    Pkg.makePrologue = "vpath %.c C:/temp";

    and then use short names in your package.bld.