• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 8491 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Changing Debug.lkf

gg52742
Prodigy 90 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I use CC v3.3 to build my project (I do not use the makefile).  The following is an excerpt from my build log.  I am wondering how to change the link file, debug.lkf.  I could not see anything in the spru187n.pdf doc.  I'm sure this is easy, but can anyone help?  What I am trying to do is make two different builds with the same source files withotu having to clean the previous build.  Thanks!!


[ufpga.cpp] "C:\Program Files\Texas Instruments\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -k -rtti -as -ox -ol1 -o3 -fr"./debug33rom" -fs"./debug33rom" -ft"./debug33rom" -d"_DEBUG" -d"AE_SOL" -d"PWM_DAC" -mo -ml3 -mr1 -mv6710 -@"../../../Debug.lkf" "ufpga.cpp"

[vectors.asm] "C:\Program Files\Texas Instruments\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -k -rtti -as -ox -ol1 -fr"./debug33rom" -fs"./debug33rom" -ft"./debug33rom" -d"_DEBUG" -d"AE_SOL" -d"PWM_DAC" -mo -ml3 -mr1 -mv6710 -@"../../../Debug.lkf" "vectors.asm"

[version.cpp] "C:\Program Files\Texas Instruments\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -k -rtti -as -ox -ol1 -fr"./debug33rom" -fs"./debug33rom" -ft"./debug33rom" -d"_DEBUG" -d"AE_SOL" -d"PWM_DAC" -mo -ml3 -mr1 -mv6710 -@"../../../Debug.lkf" "version.cpp"
"version.cpp", line 13: warning: variable "MakeThisFileCompile" was declared but never referenced

[Linking...] "C:\Program Files\Texas Instruments\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -@"Debug.lkf"
<Linking>

Build Complete,
  0 Errors, 1 Warnings, 0 Remarks.

  • 0
    TI__Guru* 84110 points

    Debug.lkf is a simple ASCII text file if you want to edit it. But it is not intended for that use. The Debug.lkf file will be generated by CCS and/or the Code Generation tools each time you do a CCS build.

    For the use of this file, search through spru187n for -@

    gg said:
    What I am trying to do is make two different builds with the same source files without having to clean the previous build.

    I am not sure what this means. But you can certainly copy Debug.lkf to a new filename and use that new filename in your own command-line calls to the compiler steps you have shown above.

     

    If this answers your question, please click the  Verify Answer  button on this reply. If not, please reply back with additional information to help us understand your question.

  • 0 in reply to RandyP
    Prodigy 90 points

    Thanks for the reply!

    I realize you cn change the filename to another in a command-line invocation of the compiler and linker.  What I don't know how to do is how to get the GUI to use a filename other than "Debug.lkf".  It seems this should be configurable in the Build Options.  But I've  not been able to locate it yet.  Any ideas on that?

  • 0 in reply to gg52742
    TI__Guru* 84110 points

    It uses the same name as used for the Build Configuration. If you do a Release build using the Release Configuration, it will use Release.lkf.

    You can duplicate the Debug Configuration and call it Debug2, for example. A Debug2 build would not use the same .obj files from the Debug build, but would recompile those files if the source has changed, etc.

    Would a Debug2 configuration meet your needs? It would use the same source files and would not clean the previously compiled files for the Debug build.

    If not, what are you actually trying to accomplish?

  • 0 in reply to RandyP
    Prodigy 90 points

     

    Thanks again for the response!

    So, are you saying I cannot change the .lkf file that the GUI uses during builds?

    You're answers are interesting because it brings up another area I was looking into.  I have a single set of cpp and h files that are common to my ROM version and my RAM version.  Then there are a few files extra in the ROM version that do not exist in the RAM version and vice-versa.  There are also unique .cmd link files.  What I would like to do is throw all of these files (common + ROM-only + RAM-only) into a single directory and be able to build a ROM version and a RAM version without having to clean builds in between and, if possible, make this all happen from the same project.  Is it possible to set up a Debug Configuration with the common set of files plus a unique link file and a few others and then a Release Configuration with the common set of files plus a unique link file and a few different others?  From your info so far, it sounds like maybe I could.

    Either I could make a Debug and Debug2 or a Debug and a Release setup?

  • 0 in reply to gg52742
    TI__Guru* 84110 points

    This thread belongs in the Code Composer Forum, so I have moved it here to get the best visibility by the CCS experts.

    You can easily create separate ROM and RAM build configurations within your project. They can start as exact copies of the Debug or Release configurations, then you can change anything within them as you need.

    The ability exists to exclude files from the build within a configuration, so I believe the best way to do what you want is to have all the files included in the project, including both linker command files, then exclude the files that you do not want for either the ROM build or the RAM build.

    I spent a few minutes but could not find the CCS User's Guide that would have good descriptions of the Build Configuration process and capabilities. Perhaps someone else will join in with a pointer to that document. CCS 3.3 has some pretty useful online Help files, so try looking there, from the Help menu item in CCS 3.3.

  • 0 in reply to RandyP
    Prodigy 90 points

    Ok, thanks!

    I just some other help from the CCS Help->Content menu.  Duh, I was looking for a pdf.  I think I'll have to play a little and do some more reading.  I'm new (obviously!) and my coding deadlines have been preceding my time to get up to speed on CCS.  Anyway, you have been very helpful!  Thanks.

  • 0 in reply to gg52742
    TI__Mastermind 18130 points

    gg said:

     

    Thanks again for the response!

    So, are you saying I cannot change the .lkf file that the GUI uses during builds?

    You're answers are interesting because it brings up another area I was looking into.  I have a single set of cpp and h files that are common to my ROM version and my RAM version.  Then there are a few files extra in the ROM version that do not exist in the RAM version and vice-versa.  There are also unique .cmd link files.  What I would like to do is throw all of these files (common + ROM-only + RAM-only) into a single directory and be able to build a ROM version and a RAM version without having to clean builds in between and, if possible, make this all happen from the same project.  Is it possible to set up a Debug Configuration with the common set of files plus a unique link file and a few others and then a Release Configuration with the common set of files plus a unique link file and a few different others?  From your info so far, it sounds like maybe I could.

    Either I could make a Debug and Debug2 or a Debug and a Release setup?

    Someone pointed out an article to me written for the C28xx specifically, but the principles are the same and should apply to your project as well. Please take a look at this page as it also discusses creating a single project with both a RAM and ROM build.

  • 0 in reply to gg52742
    TI__Guru**** 450761 points

    gg said:
    So, are you saying I cannot change the .lkf file that the GUI uses during builds?

    No, those names cannot be changed from the default that CCS uses.

  • 0 in reply to Ki
    Prodigy 90 points

    Thank you for your response.  Tim already sorted me out last month.