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.

Rebuilding driverlib - "Warning: nothing to build"

Other Parts Discussed in Thread: MSP430WARE, MSP430F5529, MSP430F5528, MSP430FR5969, MSP430FR6989, MSP430F5635, MSP430F5632

I am trying to rebuild the MSP430Ware driverlib as outlined here processors.wiki.ti.com/.../Creating_TI-RTOS_Projects_for_Other_MSP430_Devices, but it is giving me the message "Warning: nothing to build", and doesn't seem to build anything. This is the output from command line:

C:\ti\tirtos_cc13xx_cc26xx_2_20_00_06>..\xdctools_3_32_00_06_core\gmake.exe -f tirtos.mak drivers
building tirtos drivers...
gmake[1]: Entering directory `c:/ti/tirtos_cc13xx_cc26xx_2_20_00_06/products/tidrivers_cc13xx_cc26xx_2_20_00_08'
building drivers packages ...
c:/ti/xdctools_3_32_00_06_core\packages\xdc\bld\xdc_top.mak:267: Warning: nothing to build; the directories named after -P[RrD] don't contain any buildable packages
-P
-Pr
-PR
-PD
making all: Thu Oct 6 16:46:28 EST 2016 ...
.interfaces files complete: Thu Oct 6 16:46:28 EST 2016.
.libraries files complete: Thu Oct 6 16:46:28 EST 2016.
.dlls files complete: Thu Oct 6 16:46:28 EST 2016.
.executables files complete: Thu Oct 6 16:46:29 EST 2016.
all files complete: Thu Oct 6 16:46:29 EST 2016.
gmake[1]: Leaving directory `c:/ti/tirtos_cc13xx_cc26xx_2_20_00_06/products/tidrivers_cc13xx_cc26xx_2_20_00_08'

  • Jason Ku said:
    C:\ti\tirtos_cc13xx_cc26xx_2_20_00_06>..\xdctools_3_32_00_06_core\gmake.exe -f tirtos.mak drivers
    building tirtos drivers...

    Did you modify your tirtos.mak file to conform to your setup?

    Can you attach or paste your tirtos.mak file?

    Jason Ku said:
    gmake[1]: Entering directory `c:/ti/tirtos_cc13xx_cc26xx_2_20_00_06/products/tidrivers_cc13xx_cc26xx_2_20_00_08'
    building drivers packages ...
    c:/ti/xdctools_3_32_00_06_core\packages\xdc\bld\xdc_top.mak:267: Warning: nothing to build; the directories named after -P[RrD] don't contain any buildable packages

    It would seem that your filesystem is not right.  XDC is looking for package.bld files below your c:/ti/tirtos_cc13xx_cc26xx_2_20_00_06/products/tidrivers_cc13xx_cc26xx_2_20_00_08/packages' directory.  Let's check for one in particular - do you see a package.bld file in c:/ti/tirtos_cc13xx_cc26xx_2_20_00_06/products/tidrivers_cc13xx_cc26xx_2_20_00_08/packages/ti/drivers?

    Regards,

    - Rob

  • Hi Robert,

    I just realized I was trying to build MSP430 drivers inside the CC13xx/26xx folder, so I tried it again from C:\ti\tirtos_msp43x_2_16_01_14, but got the same warning message. I did find a package.bld file in c:\tirtos_msp43x_2_16_01_14\products\tidrivers_msp43x_2_16_01_13\packages\ti\drivers, and I was able to rebuild the driverlib for a different board a few months ago, so I'm not sure what changed.

    In tirtos.mak, the only 3 lines I changed were the compiler locations, and the MSP430DEVLIST:

    1. ti.targets.msp430.elf.MSP430X ?= $(TI_INSTALL_DIR)/ti-cgt-msp430_15.12.1.LTS
    2. ti.targets.arm.elf.M4F ?= $(TI_INSTALL_DIR)/ti-cgt-arm_16.3.0.STS
    3. MSP430DEVLIST := MSP430F5528,MSP430F5529,MSP430F5632,MSP430F5635,MSP430FR5969,MSP430FR6989

    I tried reinstalling TI-RTOS and the warning was gone, but I had some conflicts from a separate IDE that I installed recently, which seemed to have added DEFAULT_INSTALL_DIR to the PATH environment variable, and was causing the wrong compiler to be used. I removed the other entry from the PATH, and was able to build the ti drivers, but I am now getting an error when trying to build msp430 driverlib to build the .lib files (e.g. C:\ti\tirtos_msp43x_2_16_01_14\products\msp430_driverlib_2_21_00_08a\driverlib\MSP430F5xx_6xx\ccs\MSP430F5528.lib).

    c:\ti\tirtos_msp43x_2_16_01_14>..\xdctools_3_32_00_06_core\gmake.exe -f tirtos.mak build-ccs-msp430-driverlib
    gmake[1]: Entering directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a'
    gmake[2]: Entering directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a/driverlib'
    "Building for MSP430F5528 for the MSP430F5xx_6xx Family"
    gmake[3]: Entering directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a/driverlib'
    "making library directory"
    The syntax of the command is incorrect.
    gmake[3]: *** [mklib] Error 1
    gmake[3]: Leaving directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a/driverlib'
    gmake[2]: *** [MSP430F5528] Error 2
    gmake[2]: Leaving directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a/driverlib'
    gmake[1]: *** [all] Error 2
    gmake[1]: Leaving directory `c:/ti/tirtos_msp43x_2_16_01_14/products/msp430_driverlib_2_21_00_08a'
    gmake: *** [build-ccs-msp430-driverlib] Error 2

    Thanks,

    Jason

  • Jason Ku said:
    "making library directory"
    The syntax of the command is incorrect.

    I was able to reproduce the problem.

    It appears that there is an error in the Makefile in C:\ti\tirtos_msp43x_2_16_01_14\products\msp430_driverlib_2_21_00_08a\driverlib\MSP430F5xx_6xx (and probably every other Makefile in "peer" Makefiles in the other subdirectories of driverlib).

    The problem is that the $(MKDIR) command is using forward slashes but it needs backslashes.  I was able to fix this by replacing them with backslashes:
    # Create target directory
    mklib:
            @echo "making library directory"
            $(MKDIR) $(FAMILYDIR)\$(COMPILER)\$(FAMILYDIR)

    But then you will probably hit the problem with the clean-objects target.  It contains a Linux "rm -rf" command.  This can be changed to "del", and again the forward slashes need to be changed to backslashes.  But if you rerun your 'gmake' after the failure, it will complain that the directory it wants to $(MKDIR) already exists.  You can delete the 'ccs' directory under MSP430F5xx_6xx and proceed after that.

    I'm getting the feeling that a unix-like shell is required for the PC, such as the Cygwin shell, to accommodate all these Linux-isms, but you might not have such a shell.  But if you do the "fixes" I've specified here in this Makefile and other "peer" Makefiles then you should be able to use a regular DOS command window.

    Regards,

    - Rob

  • Hi Robert,

    I forgot I had Cygwin installed, which is probably what I used for my previous build. I was able to rebuild the driverlib .libs using Cygwin with no problem.

    Thanks,
    Jason