• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 1896 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.

CCS 5.0.3.00028 Headless Build Requires X

Dan Christensen
Prodigy 240 points

Other Parts Discussed in Thread: TEST2, CCSTUDIO

Hello,

I am trying to perform a headless build (for the purposes of continuous integration), but am getting an error whenever I try the build without some kind of X server running, with the DISPLAY environment variable set.

This is easily reproduced by creating a new workspace ('test'), and then a new project ('simple') based on the "Hello World" example.

Then, invoke the headless build, importing the existing project into a new workspace:
install/ccsv5/eclipse/jre/bin/java -jar install/ccsv5/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -import test/simple -build simple/Debug -data test2 -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole

This results in the following console messages:
Create.
Opening 'simple'.
Refreshing '/simple'.
Managed Build system manifest file error: Could not load value handler com.ti.ccstudio.managedbuild.core.options.OutputFileOptionValueHandler in option com.ti.ccstudio.buildDefinitions.C6000_7.2.compilerID.OUTPUT_FILE.

Managed Build system manifest file error: Could not load value handler com.ti.ccstudio.managedbuild.core.options.OutputFileOptionValueHandler in option com.ti.ccstudio.buildDefinitions.C6000_7.2.linkerID.OUTPUT_FILE.1558814483.

Managed Build system manifest file error: Could not load value handler com.ti.ccstudio.managedbuild.core.options.OutputFileOptionValueHandler in option com.ti.ccstudio.buildDefinitions.C6000_7.2.linkerID.OUTPUT_FILE.1558814483.

Managed Build system manifest file error: Could not load value handler com.ti.ccstudio.managedbuild.core.options.OutputFileOptionValueHandler in option com.ti.ccstudio.buildDefinitions.C6000_7.2.linkerID.OUTPUT_FILE.1558814483.

Managed Build system manifest file error: Could not load value handler com.ti.ccstudio.managedbuild.core.options.OutputFileOptionValueHandler in option com.ti.ccstudio.buildDefinitions.C6000_7.2.linkerID.OUTPUT_FILE.1558814483.

The workspace log is also attached:
0434.workspace.log.txt

The only workaround I could think of was to use xvfb, which is what I'm doing for now.  I haven't tested to see if it is fixed in the latest version, but I did see a similar issue which was.

Thanks,
Dan

  • 0
    TI__Guru**** 483681 points

    Hi Dan,

    It looks like you are using the commands for v4. The commands have been updated for v5. See:

    http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create#Working_with_CCSv5

    Thanks

    ki

  • 0 in reply to Ki
    TI__Genius 15910 points

    Ki, Dan, 

    The command that Dan is using is actually a CDT command rather than CCS. However, CCS headless commands have the same issue in that they need to have a valid DISPLAY configured. The only workaround that exists today is to configure xvfb as Dan has already done. 

    Martin

  • 0 in reply to MartinS
    Prodigy 240 points

    Martin,

    Thanks for the quick reply.  Is there any plan to remove the valid DISPLAY requirement for headless builds?

    Thanks,
    Dan

  • 0 in reply to Dan Christensen
    Intellectual 620 points

    Dan Christensen said:

    Martin,

    Thanks for the quick reply.  Is there any plan to remove the valid DISPLAY requirement for headless builds?

    Thanks,
    Dan

    I, too, am voting for this to get done.  I am running into the same exact error.

    Dan, I assume you are using Jenkins or Hudson?

  • 0 in reply to Judson Wilson
    TI__Genius 15910 points

    Dan, 

    You are currently using a standard eclipse command. Unfortunately, the best I can offer is to suggest filing a bugzilla with community. CDT project's main page is at link below:

    http://www.eclipse.org/projects/project.php?id=tools.cdt


    CCS equivalent commands to do headless builds are documented here. Currently, they have the same issue. However, I have filed a new bug report requesting to support building of projects without DISPLAY configured. The id for this is SDSCM00043588 and you can track it status using link below. 

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDo-Web&contextid=SDOWP&username=readonly&password=readonly

    Martin

  • 0 in reply to MartinS
    Prodigy 240 points

    Judson Wilson said:

    Dan, I assume you are using Jenkins or Hudson?

    TeamCity for continuous integration.

    MartinS said:

    Dan, 

    You are currently using a standard eclipse command. Unfortunately, the best I can offer is to suggest filing a bugzilla with community. CDT project's main page is at link below:

    http://www.eclipse.org/projects/project.php?id=tools.cdt


    CCS equivalent commands to do headless builds are documented here. Currently, they have the same issue. However, I have filed a new bug report requesting to support building of projects without DISPLAY configured. The id for this is SDSCM00043588 and you can track it status using link below. 

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDo-Web&contextid=SDOWP&username=readonly&password=readonly

    Martin

    I've been using CDT through the Xilinx SDK to perform headless builds since their v12.1 tools (which uses CDT 6) through their current release (v13.4, which uses CDT 7.0.2).  I noticed that CCS 5.0.3 uses CDT 7.0.1.  The log I attached also indicates that the "standard eclipse command" is certainly running "CCS stuff" in order to perform the build.  This, along with the past experience using Xilinx's modified eclipse environment, makes me skeptical of the DISPLAY requirement being introduced in a version of CDT.

    That being said, I'm not an eclipse expert.  If it is a CDT issue, and a bug being filed would be useful, I would ask that your end file the issue with the CDT developers.  From my perspective, TI is my tool vendor for this particular issue.

    Thanks again for your time,
    Dan