• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 244 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.

makefile design improvement in gcc folders

sang gang
Intellectual 300 points

Hi,

I successfully compiled sample projects using 'make' tool with the latest version of CodeSourcery Toolchain. It seems very well organized and easy to understand how to navigate folders.

There are two minor issues (not a bug) that I really hope to be patched in the next version of StarterWare. That should be very straight forward. (I'm just so lazy to modify all those makefiles). I'm not sure if this is the same case for older version (2009q1) of CodeSourcery that TI website provides.

1. Whenever I type 'make' in a folder, say gpio, it compiles all necessary libraries again from scratch. The makefile generates all intermediate files (*.o* files) again and archive them again. I'm not good at 'make' tool. But there should be an option or a way to inhibit this behavior.

2. Let's say I 'make' a file once, successfully. Then, if I run 'make' again, then I always get an error message saying

      Release/gpioLEDblink.out: file not recognized: File truncated

Could you fix this behavior so that I don't have to 'make' again?

If there are quick fixes for these behaviors, that would be great.

Thanks a lot.

SG

ps. One more thing. The bootloader can be compiled with the latest version of CodeSourcery, but never really boot-up. I painfully figured out that the booting procedure cannot pass a function, "HSMMCSDImageCopy(void)", because the temporary filename was not correctly produced and therefore the whole system hangs (I'm using beaglebone). Instead of the line "strcat(g_cTmpBuf, "app")", I manually typed in the file name.

    g_cTmpBuf[0]='/';
    g_cTmpBuf[1]='a';
    g_cTmpBuf[2]='p';
    g_cTmpBuf[3]='p';
    g_cTmpBuf[4]='\0';
This makes sure that I use the right filename without string manipulations. (Interestingly, CCSv5-complied MLO didn't show this symptom.)
  • 0
    TI__Intellectual 2525 points

    hi Sang,

    Thanks a lot for your feedback ! We will definitely consider the suggestion to eliminate the issues on GCC make behavior you pointed out.

    Regarding the latest version of Code Sourcery, we suggest to use the version given in the user guide as we may not test it in different versions of the tool chain. However, if we update the version,  we will definitely document it.

    Regards,

    Sujith.