[patch] plugin directory / common location for plugins

Basile Starynkevitch basile@starynkevitch.net
Mon Mar 29 16:39:00 GMT 2010


Matthias Klose wrote:
> On 28.03.2010 16:34, Basile Starynkevitch wrote:
>> Basile Starynkevitch wrote:
>>> Matthias Klose wrote:
>>>> On 27.03.2010 14:45, Matthias Klose wrote:
>>>>> Attached is an updated patch for the plugin directory, changes 
>>>>> compared
>>>>> to the version posted at
>>>>> http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00644.html :
>>>>>
>>>>> - removal of the extra "libexec" subdirectory.
>>
>> I forgot to say that...
>>
>> We might want to put the plugins .so files into some subdirectory, which
>> probably should be better "lib" than "libexec". But this is a small
>> detail (and is always a convention).
> 
> cc1, *.[ao], ... aren't in a subdirectory either. why should the plugin 
> code go into a subdirectory?


I definitely don't care that much about putting a subdirectory or not. 
However, the plugin directory currently contains only one directory 
(include/) - and in that respect is more something like /usr [which 
contains mostly directories on today's Linux] than like /lib |which 
contains mostly *.so files].

But really, this is a tiny detail I don't care that much. Do what you 
want, it is not that important (so my considerations afor a lib 
subdirectory inside the plugin directory are more a matter of taste than 
a matter of reason).

What is important is:

* the ability to have short plugin names

* a function to be able to query from plugins the plugin directory.

FWIW, the MELT plugin need several sub-directories (in particular one 
for the MELT source files *.melt & generated *.c, and another for the 
MELT modules *.so; all are handled by the melt.so plugin).

I hope this patch will go into 4.5.

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} ***



More information about the Gcc-patches mailing list