public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: [rfc] common location for plugins
  2010-03-23 18:29 [rfc] common location for plugins Matthias Klose
@ 2010-03-23 18:29 ` Basile Starynkevitch
  0 siblings, 0 replies; 2+ messages in thread
From: Basile Starynkevitch @ 2010-03-23 18:29 UTC (permalink / raw)
  To: Matthias Klose; +Cc: gcc, GCC Patches

Matthias Klose wrote:
> For packages of GCC I would like to see a common location where plugins 
> can be installed; currently a path to the plugin has to be given on the 
> command line, which is likely to be different for different 
> installations.  What about -fplugin=<name> (without the .so) meaning to 
> search for the plugin in a default location like <gcclibdir>/plugins for 
> the plugin? -fplugin=<name>.so could also be used, but maybe would be 
> ambiguous looking in the current dir, or the plugin dir.


I did posted on gcc-patches@ many times a patch providing exactly that 
feature, but nobody reviewed it.

Last post of the patch is 
http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00644.html

Given Matthias wish, I dare ping again that patch....

Cheers.

-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [rfc] common location for plugins
@ 2010-03-23 18:29 Matthias Klose
  2010-03-23 18:29 ` Basile Starynkevitch
  0 siblings, 1 reply; 2+ messages in thread
From: Matthias Klose @ 2010-03-23 18:29 UTC (permalink / raw)
  To: gcc

For packages of GCC I would like to see a common location where plugins can be 
installed; currently a path to the plugin has to be given on the command line, 
which is likely to be different for different installations.  What about 
-fplugin=<name> (without the .so) meaning to search for the plugin in a default 
location like <gcclibdir>/plugins for the plugin? -fplugin=<name>.so could also 
be used, but maybe would be ambiguous looking in the current dir, or the plugin dir.

   Matthias

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-03-23 18:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-23 18:29 [rfc] common location for plugins Matthias Klose
2010-03-23 18:29 ` Basile Starynkevitch

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).