|
|
Home » Developing U++ » U++ Developers corner » pkg-config discussion
pkg-config discussion [message #8590] |
Tue, 20 March 2007 14:31 |
ebojd
Messages: 225 Registered: January 2007 Location: USA
|
Experienced Member |
|
|
This is probably still a little early, but if it would not take to much time away from other things I would like to start a discussion on adding pkg-config to U++.
While I have not invested a lot of time in implementation and testing, I had played with a simple hack which allowed me to execute a a generic script to grab the configuration information. The problem with this approach, as I had alluded previously, is that there are a number of computer systems security issues that should be addressed so that users cannot gain inappropriate access to system resources or run malicious scripts.
The flip side to this problem is that we do not know ahead of time *all* the package configuration tools that we will need to query. Therefor allowing U++ to run generic scripts during the build process allows the greatest functionality.
One other possibility is to develop a tool that will help cache and manage configuration info when U++ is built and installed. This will sidestep most of the subtler sys admin issues, but will complicate using configuration scripts for user applications.
I have a number of ideas and solutions for each of these design ideas, but will end the post here to solicit thoughts on the matter.
Best regards,
EBo --
|
|
|
Re: pkg-config discussion [message #8591 is a reply to message #8590] |
Tue, 20 March 2007 14:41 |
|
mirek
Messages: 13984 Registered: November 2005
|
Ultimate Member |
|
|
Well, do not wory, `pkg-config` is coming. The real roadblock is still missing final 2007.1 release. I do not dare to change things too much now. Once we are back on dev version release cycle, this is one of first things to happen.
I do not plan to do anything complicated, just to "interpret" strings in Package organizer before being used - scan for ` and perform command if needed (most likely just once per compilation).
This way, all that is needed is to put pkg-config call into linker and compiler options. Not very elegant, but portably working, and that is all that is important...
Of course, more elegant solution would be to put it somehow into libraries / includes, but the trouble there is that pkg-config seems to return actual command-line elements, therefore conversion back to directories / lib names would be needed.
Mirek
|
|
|
|
|
|
|
|
|
Re: pkg-config discussion [message #8632 is a reply to message #8627] |
Thu, 22 March 2007 03:57 |
ebojd
Messages: 225 Registered: January 2007 Location: USA
|
Experienced Member |
|
|
guido wrote on Wed, 21 March 2007 16:04 |
autotools makes it easy to kind of shrink-wrap binaries onto any number of subtly different varieties of (mainly) POSIX ABIs. autotools plays a significant role in proliferation of Linux's self-incompatibilities.
Since this is an ISV anti-feature, it would be overkill, at best.
|
I jsut had my browser dump my detailed reply and I am calling it quits for the night... Oh well...
In short I agree with Guido. It was an "off the top" brainstorming idea which I had not thought through. Hacking in running the scripts will work, but we should address the security issues as part of the discussion and development. The plus side is that it should be relitively easy to get it up and running...
EBo --
|
|
|
Goto Forum:
Current Time: Mon Jun 10 14:14:37 CEST 2024
Total time taken to generate the page: 0.01208 seconds
|
|
|