This is the mail archive of the
mailing list for the GCC project.
Re: adding support for vxworks os variants
- From: Olivier Hainque <hainque at adacore dot com>
- To: gcc at gcc dot gnu dot org
- Cc: Olivier Hainque <hainque at adacore dot com>, nathan at codesourcery dot com, Joel Brobecker <brobecker at adacore dot com>
- Date: Mon, 19 May 2014 16:06:56 +0200
- Subject: Re: adding support for vxworks os variants
- Authentication-results: sourceware.org; auth=none
- References: <9E25E4A8-93DA-4AD8-8B85-8F8C38E8042C at adacore dot com>
On May 19, 2014, at 15:41 , Olivier Hainque <firstname.lastname@example.org> wrote:
> For vxsim or smp, having entirely separate toolchains with different triplets
> for so minor differences seemed overkill and impractical for users, so we have
> added "-vxsim" and "-vxsmp" command line options to our toolchains to help.
> We have done the same for the cert variants, with a "-vxcert" command line
> option, but wonder if a separate triplet wouldn't actually be better in this
> One small concern is that the system toolchains don't know about the new
> options, and we think that it might be of interest to minimize the interface
> Thoughts ?
One point I forgot to mention: we have considered the use of external spec
files as an alternative strategy. We have started experimenting with it and
don't yet have a lot of feedback on this scheme.
Your opinion on this alternate option (how much more viable/flexible/acceptable
it would likely be) would be most appreciated.
I'm of course happy to provide extra details on what we have been doing if