• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 833 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.

CCSv4 Not producing relocatable object file

Javier Malave-Bonet
Expert 5805 points


Code Generation Tools: 6.1.12

Compiler: 6lx

Target: 64+

Endiannes: little

Runtime support library: rts64plus.lib

I am trying to produce a relocatable object file of my source but when I indicate the output extension to be .obj in the linker settings; the compiler automatically tries to build the target without compiling any of the sources and the linker is never invoked. Apart from full symbolic debug option and Diagnostic set to 225 I have no other option selected in the compiler settings. Preprocessor Parser and Directory Specifier are set to Automatic. My configuration name is: Release

However a regular (non-relocatable) .out file is generated perfectly. My code compiles and runs fine on the target destination. This configuration I named: Debug. To create Release I merely copied Debug settings to Release, selected "produce relocatable object file" and changed the output extension to .obj.

Any ideas why this would happen? I greatly appreciate your attention.

Sincerely,

Javier

  • 0
    TI__Guru**** 173310 points

    Javier,

    Which  version of CCS are you using? Can you copy and paste the complete output of the CCS console window and attach it to the post? This might give us more clues as to what is happening. There shouldn't be an issue with specifying the output file name of relocatable link with .obj extension as long as the name is different from any of the source file names.

  • 0
    TI__Guru**** 251690 points

    If I understand what you want to do correctly, the only difference between your project and an ordinary executable project is that you need to use one more linker option: --relocatable.  Just leave the final output file extension at ".out".  It doesn't have to be ".obj".  

    Thanks and regards,

    -George

     

  • 0 in reply to George Mock
    TI__Expert 5805 points

    Hi All, 

    Thanks for your inputs. Below is the log CCS outputs when trying to generate the .obj file. The CCS version is v4. 

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all

    'Building target: C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/testrel/avpaex0181/avpaex0181.obj'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv64+ -g --define=CCS --define=QT --define=NO_XDC --define=DDR_QT --define=FULL --define=NY --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/pa/fw" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/pa/src" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/cppi" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/pa" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/pa/test/PAUnitTest/" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/qmss" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/qmss/device" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/csl/" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/csl/src/intc" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/common/include_n/" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/pass/modules/common_inc" --include_path="C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/pass/modules/ctr02_p1/inc" --diag_warning=225 --obj_directory="common_src" 

     

    Then it will list every single source file of the build:

     

    "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/cppi/src/cppi_desc.c" "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/cppi/device/cppi_device.c" "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/PDK/pdk_c6498_1_0_0_6/packages/ti/drv/cppi/src/cppi_drv.c" "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/common/src_n/ddr3_setup_CSL.c"

    .

    .

    .

     

    Then it will claim build is complete:

     

    [pa_utils.c]

    [pkttxrx.c]

    [eth_utils.c]

    [ex1util.c]

    [expa.c]

    [new_setupqm.c]

    [pktgen.c]

    "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/pass/modules/common_src/pktgen.c", line 217: warning: integer conversion resulted in truncation

    "C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/pass/modules/common_src/pktgen.c", line 224: warning: integer conversion resulted in truncation

    [test_main.c]

    'Finished building target: C:/ccs_a0866755_sps_vw/nysh_avv_a0866755/nysh_avv/data_catapps/nysh/testrel/avpaex0181/avpaex0181.obj'

    ' '

    Build complete for project ctr02_p1

    As you can see, Compiler is invoked to generate the final target avpaex0181.obj without having compiled any of the source files before hand. Then linker is never invoked to produce the relocatable object file. I have added the --relocatable in the linker command line, but again linker is never invoked.

     

    Thanks for your time and help.

     

    Regards,

    Javier

  • 0 in reply to Javier Malave-Bonet
    TI__Expert 5805 points

    Hi George,

    I am from Ti Employee from Houston site. If you are local we can meet in the cafeteria on Bldg 2 to discuss. I would greatly appreciate your help.

    Regards,

    Javier

  • 0 in reply to Javier Malave-Bonet
    TI__Expert 5805 points

    Thanks to everyone. I solved the problem.

     

    Regards,

    Javier

  • 0 in reply to Javier Malave-Bonet
    TI__Expert 5805 points

    Hi all,

    For the benefit of everyone the solution to the problem is more truthfully a workaround. The original project itself is still not generating the .obj file, but I created a new project, included all the source files again and everything works. It seems my old project files either got corrupted or got stuck with some setting that is causing the unexpected behavior.

    Regards,

    Javier