C and CPP specific settings

[GregDomjan]

The C folder split from the CPP folder, however compilers appear to only be configured in CPP mode.

Believe the aol properties is not currently configured to make this difference, both are treated as CPP.
http://msdn.microsoft.com/en-us/library/032xwy55.aspx
http://stackoverflow.com/questions/172587/what-is-the-difference-between-g-and-gcc

In particular should we add a whole linker definition for gpp when it represents the c++ compiler name or should it be a part of the GCC linker.

[dscho]

There are some *.c.* entries in aol.properties with a suspicious comment about NAR-6 above them. However, I seem to be unable to find NAR-6. Any clue?

[ctrueden]

@dscho NAR-6 refers to an issue in the Sonatype bug tracker. There used to be a NAR category in there for all the NAR bugs. But unfortunately, they deleted it wholesale, leaving us no opportunity to migrate the issues. IIRC I even tried checking the Wayback Machine for the issues and couldn't retrieve them from there either. So they are sadly completely lost.

[GregDomjan]

NAR-6 was freehep NARPLUGIN-137 if that helps... I couldn't find anything more.

Seems from ant-contrib LinkerEnum that the linker is actually being chosen different for gcc and g++

            new ProcessorEnumValue("gcc", GccLinker.getInstance()),
            new ProcessorEnumValue("g++", GppLinker.getInstance()),

Would that mean for nar aol.config that

• should be seperate linker definitions for gcc & gpp
• gcc linker should not have a cpp section, and
• gpp linker should point to gpp for the c.compiler

[dscho]

@GregDomjan I cannot say that I really understand the issue deeply, but I trust your judgement.

[dscho]

@GregDomjan so... what's the status of this ticket? You seem to have a much better understanding of the issues and the code involved, so I assign this to you. Please address, or close, whatever you see fit.