On Wed, 10 Aug 2016 01:52:29 +0100 "M. J. Everitt" <m.j.ever...@iee.org> wrote:
> On 10/08/16 01:39, Lei Zhang wrote: > > 2016-08-09 13:58 GMT+08:00 Fabian Groffen <grob...@gentoo.org>: > >> As a question to Lei, I'm wondering why you chose eselect compiler, and > >> not gcc-config to manage the links. In a way, gcc-config is tailored > >> towards gcc, but it does a lot of things also for the environment. With > >> clang, from my experience, you just want it as drop-in replacement for > >> gcc as it doesn't give you too much issues (on Darwin at least). > > In its current form, gcc-config specializes in handling different > > versions of gcc. If we extend it to cover other compilers (and rename > > it to cc-config as James suggested), should it handle different > > versions of clang? What about different versions of icc? > > > > I'm just afraid gcc-config would become too complex that way, so I > > prefer a simpler approach: let eselect-compiler be version-agnostic. > > Then we can have clang-config to handle the versioning of clang, > > icc-config to handle icc, etc. > > > > > > Lei > > > Extending the ideas presented in this thread .. you could introduce > cc-config, and which utility script it runs would then be governed by > eselect compiler .. eg. gcc would have gcc-config, clang would run > clang-config .. .. to switch between the one version of clang that can be installed? -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgpkxSSO5MOFn.pgp
Description: OpenPGP digital signature
