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

CCSv6 Linux Bug: Unable to manage build configurations

John Boyd1
Prodigy 220 points

Hi,

I am using CCSv6 on my Linux machine running Linux Mint 17 32bit. The options to manage build configurations and exclude resources from particular configurations do not seem to be working. I can create a new build configurations and exclude resources from other build configurations except resources that are used in the primary "debug" configuration. All resources included in the debug configuration are built even if I am not using the debug configuration.

I am not sure if this is a bug or a strange feature that I am not familiar with.

Thanks,

John

  • 0
    TI__Guru**** 161575 points

    John,

    It is working ok for me on Windows.  I will have access to a machine with Linux Mint on it tomorrow that I can try.  One thing to watch out for is that there are several build commands.  One of them builds all projects and configs. 

    If you select the drop down arrow beside the build button and click on the configuration there does it build correctly?

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 220 points

    No, I tried that and it still builds all sources included in the "debug" configuration.

  • 0 in reply to John Boyd1
    TI__Guru**** 161575 points

    It is working ok for me on Linux Mint

    Here is my Debug configuration.  You can see that john.c is included in the configuration.

    Here is my release configuration.  You can see that john.c is excluded.

    Here is the output when I build the Debug config.  You can see that john.c is built.

    Now here is the output when I build the release configuration.  John.c is not built.

    Further if I look in the Release config folder there is no obj file for john.

    How are you excluding files from the build?  I am wondering if you are moving them into the config folder.  If so that doesn't exclude them.  To exclude them switch to the config you want (right click on the project, Select Build Configurations -> Set Active -> Choose the one you want).  Then right click on the files you want to exclude and select "Exclude from Build".

  • 0 in reply to JohnS
    Prodigy 220 points

    Hmmm, that is interesting. That is the exact same procedure I use to exclude resources from build configurations, but it does not work for me. I do this on my home computer, so when I get off work today, I will take screenshots of my steps and post the results.

    Thanks,

    John

  • 0 in reply to John Boyd1
    TI__Guru**** 161575 points

    If you could export your project to an archive I could try on my system and see if I get the same results using your project.  If the code is sensitive there is a way to initiate a private conversation in E2E and exchange the file.

    To export go to File -> Export.  Expand General and Select Archive file.   Then check the boxes for the projects you want to export.

    Then from the Project menu I can select import CCS project and import it from the archive.

    Attached is my project if you want to see if it works for you.  It is a Tiva project so you would need to have support for that family installed.

    5531.john.tar

  • 0 in reply to JohnS
    Prodigy 220 points

    Ok, here are some screenshots of my steps. I am also attaching a copy of my project directory.

    I created a build configuration called "Hardware test". I then excluded "main.cpp" from that build configuration:

    I then made sure "main-hardwareTest.cpp" was not excluded from this build configuration and was excluded from the others:

     I then made sure that I had selected the "Hardware Test" build configuration:

    Finally I selected build>hardware test from the build drop down menu: (immediately you can see that the wrong main file is grayed out in the project explorer.)

    I made sure that the "main.cpp" file had an error in it, so if it was compiled, it would throw an error and I would know that it compiled the wrong file:

    I checked the console output though, and it makes no mention of building the unwanted main.cpp file:

    17:26:11 **** Build of configuration Hardware Test for project BeagleBoneBlack_Flight_Computer ****
make all 
Building file: ../source/BBB-FlightComputer/hardware/L3GD20Gyro.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/BBB-FlightComputer/hardware/L3GD20Gyro.d" -MT"source/BBB-FlightComputer/hardware/L3GD20Gyro.d" -o "source/BBB-FlightComputer/hardware/L3GD20Gyro.o" "../source/BBB-FlightComputer/hardware/L3GD20Gyro.cpp"
In file included from ../source/BBB-FlightComputer/hardware/L3GD20Gyro.cpp:13:0:
../source/BBB-FlightComputer/hardware/L3GD20Gyro.h:88:39: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
Finished building: ../source/BBB-FlightComputer/hardware/L3GD20Gyro.cpp
 
Building file: ../source/BBB-FlightComputer/hardware/LMS303.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/BBB-FlightComputer/hardware/LMS303.d" -MT"source/BBB-FlightComputer/hardware/LMS303.d" -o "source/BBB-FlightComputer/hardware/LMS303.o" "../source/BBB-FlightComputer/hardware/LMS303.cpp"
In file included from ../source/BBB-FlightComputer/hardware/LMS303.cpp:14:0:
../source/BBB-FlightComputer/hardware/LMS303.h:117:41: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
Finished building: ../source/BBB-FlightComputer/hardware/LMS303.cpp
 
Building file: ../source/BBB-FlightComputer/hardware/LPS331Altimeter.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/BBB-FlightComputer/hardware/LPS331Altimeter.d" -MT"source/BBB-FlightComputer/hardware/LPS331Altimeter.d" -o "source/BBB-FlightComputer/hardware/LPS331Altimeter.o" "../source/BBB-FlightComputer/hardware/LPS331Altimeter.cpp"
Finished building: ../source/BBB-FlightComputer/hardware/LPS331Altimeter.cpp
 
Building file: ../source/BBB-FlightComputer/AHRS/ahrs.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/BBB-FlightComputer/AHRS/ahrs.d" -MT"source/BBB-FlightComputer/AHRS/ahrs.d" -o "source/BBB-FlightComputer/AHRS/ahrs.o" "../source/BBB-FlightComputer/AHRS/ahrs.cpp"
In file included from ../source/BBB-FlightComputer/AHRS/../BBB-FlightComputer.h:17:0,
                 from ../source/BBB-FlightComputer/AHRS/ahrs.h:4,
                 from ../source/BBB-FlightComputer/AHRS/ahrs.cpp:1:
../source/BBB-FlightComputer/AHRS/../hardware/LMS303.h:117:41: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
In file included from ../source/BBB-FlightComputer/AHRS/../BBB-FlightComputer.h:19:0,
                 from ../source/BBB-FlightComputer/AHRS/ahrs.h:4,
                 from ../source/BBB-FlightComputer/AHRS/ahrs.cpp:1:
../source/BBB-FlightComputer/AHRS/../hardware/L3GD20Gyro.h:88:39: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
Finished building: ../source/BBB-FlightComputer/AHRS/ahrs.cpp
 
Building file: ../source/BBB-FlightComputer/BBB-FlightComputer.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/BBB-FlightComputer/BBB-FlightComputer.d" -MT"source/BBB-FlightComputer/BBB-FlightComputer.d" -o "source/BBB-FlightComputer/BBB-FlightComputer.o" "../source/BBB-FlightComputer/BBB-FlightComputer.cpp"
In file included from ../source/BBB-FlightComputer/BBB-FlightComputer.h:17:0,
                 from ../source/BBB-FlightComputer/BBB-FlightComputer.cpp:10:
../source/BBB-FlightComputer/hardware/LMS303.h:117:41: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
In file included from ../source/BBB-FlightComputer/BBB-FlightComputer.h:19:0,
                 from ../source/BBB-FlightComputer/BBB-FlightComputer.cpp:10:
../source/BBB-FlightComputer/hardware/L3GD20Gyro.h:88:39: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
Finished building: ../source/BBB-FlightComputer/BBB-FlightComputer.cpp
 
Building file: ../source/main-hardwareTest.cpp
Invoking: Cross G++ Compiler
arm-linux-gnueabihf-g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"source/main-hardwareTest.d" -MT"source/main-hardwareTest.d" -o "source/main-hardwareTest.o" "../source/main-hardwareTest.cpp"
In file included from ../source/main-hardwareTest.cpp:13:0:
../source/BBB-FlightComputer/hardware/LMS303.h:117:41: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
In file included from ../source/main-hardwareTest.cpp:15:0:
../source/BBB-FlightComputer/hardware/L3GD20Gyro.h:88:39: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
Finished building: ../source/main-hardwareTest.cpp
 
Building target: BeagleBoneBlack_Flight_Computer
Invoking: Cross G++ Linker
arm-linux-gnueabihf-g++  -o "BeagleBoneBlack_Flight_Computer"  ./source/BBB-FlightComputer/hardware/L3GD20Gyro.o ./source/BBB-FlightComputer/hardware/LMS303.o ./source/BBB-FlightComputer/hardware/LPS331Altimeter.o  ./source/BBB-FlightComputer/AHRS/ahrs.o  ./source/BBB-FlightComputer/BBB-FlightComputer.o  ./source/main-hardwareTest.o   -lrt
Finished building target: BeagleBoneBlack_Flight_Computer

    But the output file was still not built...

    Thanks for looking into this!

    John

    7026.BeagleBoneBlack_Flight_Computer.zip

  • 0 in reply to John Boyd1
    TI__Guru**** 161575 points

    I will update my install to include Sitara support and give the project a try shortly.  You are using a slightly different method to exclude files but I just gave that a try on my project and it was ok so that didn't matter.

    One thing I noticed that is a bit different is that your PRU project is being listed as active in the project explorer vs the project for the A8.  That may be why you are seeing the wrong file as excluded.  Make your project explorer a bit wider and then click on the A8 project.  It should list the config that it is displaying information for.

    I will have an update in a few hours.

  • 0 in reply to JohnS
    Prodigy 220 points

    Yeah, I accidentally forgot to close out my PRU project when I was taking screenshots for you. I have tried this several times though with the A8 project being the only open project, and still had the same problems, so I dont think that is the cause.

  • 0 in reply to JohnS
    TI__Guru**** 161575 points

    The first thing I noticed when I imported the project is that it is not a CCS project but instead an Eclipse C project.  Thus the behaviour could be a bit different.  This is probably also why the exclusion stuff is messed up in the project explorer.  When I look at what it is showing it lists the config as "master" vs the actual config name.  Thus it is not showing the proper settings for the active config.

    I don't have your version of gcc installed so I changed the project to not stop on the first error as I get an error on each file.

    Here is what I see when set the active config to Debug and build.

    main.cpp gets built but not the main-hardwaretest version which is what is expected.


    Now I set the active config to hardware test and then build.

    Here main.cpp was not built but main-hardwaretest.cpp was.

    Thus for me it does seem to be working correctly

  • 0 in reply to JohnS
    Prodigy 220 points

    ok, that makes sense. Thanks!