This is the mail archive of the
mailing list for the Cygwin project.
Re: Avoid collisions between parallel installations of Cygwin
On Oct 21 17:42, Dave Korn wrote:
> Corinna Vinschen wrote:
> > In theory, if we use a specific
> > layout of the datastructure using unambiguous magic entry strings, there
> > wouldn't be a reason to use the .rsrc section at all. The DLL could
> > simply read the values from a global datastructure in the .data section.
> Hilarity will result the first time someone forgets and uses one of those
> magic strings in a strace printf because they wanted to dump the value of the
> setting :)
Why should somebody use the magic string in strace printf? It's
supposed to be there only for the benefit of the external tool
trying to access the properties settings. The string can be as
weird as you like, say
> However, that's just a minor hiccup. I think it would still be
> nice to use resources, because it's the system standard way of attaching
> metadata to a file and there are lots of tools that speak the format.
Using any kind of self-defined section like ".cygprops" and putting the
propoerties data into it is still a standard way of attaching data to
> cygcheck's POV it should be able to modify entries in the resource section
> using just the same binary-in-place-modification trick as you have here to
> edit the data section shouldn't it?
Sure, but it has to be hardcoded and it's in some wau reinventing the
wheel. A script is a script is a script.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com