On segunda-feira, 7 de janeiro de 2013 13.04.50, Oswald Buddenhagen wrote: > On Fri, Jan 04, 2013 at 09:23:21AM -0200, Thiago Macieira wrote: > > On sexta-feira, 4 de janeiro de 2013 09.38.31, Peter Kümmel wrote: > > > > I know how to make a relocatable shared library on Linux (find the > > > > calling > > > > function's address in /proc/self/maps) and I know it's possible with > > > > some > > > > Win32 API, but I have no clue how to do it elsewhere. Therefore, I > > > > won't > > > > do > > > > it. > > > > > > Isn't the discussion here only about paths, different to how memory > > > mapping > > > is handled? > > > > Yes, the discussion here is about paths. There's nothing about memory > > mapping. > > > > The "/proc/self/maps" above is a red herring. > > why?
It's a red herring because we're using the "maps" file to look for file paths, not for memory mapping. > you can use the above to determine the path to the current dll (QtCore). if > QLibraryInfo now only stores relative paths, this is all that's needed > to make the qt installations fully relocatable (as long as the internal > layout says intact). > i'd go as far as making this linux & windows only - systems which don't > support it can continue with the current absolute path stuff. Yes, that can be done, but I won't do it exactly because it isn't supported on all systems. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
