[build2] guess C compiler type

[Moldmann Max]

You are right, the Tasking compiler doesn't seem to be GCC based.
( https://stackoverflow.com/questions/50405396/flags-mapping-of-tasking-compiler-with-gcc-compiler )

And you might be right that I won't be able to use Build2 with this legacy compiler.

Anyway now it stops here:
c:\Tools\c166VXv3.0r3/bin\c166.exe -v
c:\Tools\c166VXv3.0r3/bin\c166.exe --version
error: unable to obtain c:\Tools\c166VXv3.0r3/bin\c166.exe signature with --version

Basically it looks to me that we could skip these steps in guess.cxx if we have an id override configured?

Also, are we now able to skip the config sub script as we now have another way to set the target in the configuration?
 

-----Original Message-----
From: Boris Kolpackov <boris at codesynthesis.com> 
Sent: Monday, October 29, 2018 8:05 AM
To: Moldmann Max <MoldmannMax at JohnDeere.com>
Cc: users at build2.org
Subject: Re: [build2] guess C compiler type

Moldmann Max <MoldmannMax at JohnDeere.com> writes:

> > C:\Tools\c166VXv3.0r3/bin/cc166.exe -v
> Usage: cc166 [options] files
> [...]

Hm, what makes you think this compiler is GCC-based? The command line interface is bizarre.

In any case, I've added support for config.{c,cxx}.{id,version,target}
variables (available in the latest staged version) which can be used to supply this information if build2 could not extract it automatically (for instance, because the compiler was "customized" beyond recognition).
For example:

$ b ... config.cxx.id=gcc-custom \
        config.cxx.version=4.0.0 \
	config.cxx.target=i386-linux-gnu
	
However, I doubt this will help in your case.