Jump to: navigation, search


Revision as of 06:33, 17 November 2011 by Ilg.livius.net (Talk | contribs)

How to run a full build?

You mention 'One way to test you have everything is to try and Export the master feature'.

Can you be more specific on how to do this?

Update: I found the master.git repository, with a single project in it, containing a build.sh, is this related to 'Export the master feature'? ilg@livius.net 11:11, 17 November 2011 (UTC)

Build errors

You mention "Select all the projects or individual. Project filter does not seems to work. It maybe easier select all, then close projects you don't need. Let the build run"

Well, I did this, I got all projects from the cdt.git and tried to Build All. Most ot the projects compiled just fine, but a few failed, and generated 2,098 errors and 22,411 warnings.

The failed ones are:

  • org.eclipse.cdt.codan.internal.ui.cxx
  • org.eclipse.cdt.core.lrparser
  • org.eclipse.cdt.core.lrparser.xlc
  • org.eclipse.cdt.launch.remote (probably because I did not install remote launch support)
  • org.eclipse.cdt.test.dsf

I closed them, together with the following dependencies

  • org.eclipse.cdt.core.lrparser.xlc.tests
  • org.eclipse.cdt.core.parser.upc
  • org.eclipse.cdt.core.parser.upc.tests

I cleaned everything and a new Build All generated only 182 errors and 18,263 warnings.

I further closed

  • org.eclipse.cdt.codan.checkers.ui
  • org.eclipse.cdt.core.lrparser.tests
  • org.eclipse.cdt.managedbuilder.xlupc.ui
  • org.eclipse.cdt.managedbuilder.bupc.ui

and the dependency: org.eclipse.codan.core.tests

This time I got 0 errors and 18,023 warnings.

However, I'm not sure this is the best approach to building CDT, I think a safer method should exist. ilg@livius.net 11:33, 17 November 2011 (UTC)