variables given thru shell commands in *.pc files

Tollef Fog Heen tfheen at err.no
Fri Sep 20 16:04:40 PDT 2013


]] Basile Starynkevitch 

> MELT code is translated into C++ which is then compiled (by running make internally)
> and then dlopen-ed.
> 
> Sometimes, that code may require some external package. I have a syntax 
> to facilitate using pkg-config when compiling that generated C++ code
> (search for USE-PACKAGE-FROM-PKG-CONFIG in 
> http://gcc-melt.org/meltpluginapi.html which is a very big generated HTML page)

Doesn't libdl handle this for you dynamically using dependencies between
libraries?

> I was thinking of adding some syntax to get pkg-config variables shell expanded. 

[...]

> I would believe that such feature might be easy to implement (basically, calling popen).
> I do admit that it may open security risks (since some command is arbitrarily run).
> 
> What do you think of all that? Or is there some other ways to do that?

I think it's crazy and we should not do that.  The pkg-config data is
parseable, not executable.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


More information about the pkg-config mailing list