Relocation Notes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Techniques: | Techniques: | ||
* KDE Applications | * KDE Applications | ||
** KStandardDirs class | ** [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/classKStandardDirs.html KStandardDirs] class | ||
Interesting resources: | Interesting resources: | ||
Revision as of 17:22, 10 March 2010
Techniques:
- KDE Applications
- KStandardDirs class
Interesting resources:
- Relocation macros in the Autoconf Macro Archive
- Autopackage project
- Apbuild / Apgcc
- Guide to Making Relocatable Applications (BinReloc 2.0)
- Gnulib relocation macro(s)
- The nixpkgs project uses a few techniques for working around relocation issues, but the main one appears to be a "wrapper generator" script to create wrappers that set env vars.
- For .NET software using the Mono framework, see http://www.mono-project.com/Guidelines:Application_Deployment#Relocation.
- Producing relocatable packages with the GNU build system
- Tablet Python #1 - Relocatable Software
- Relocatable Wrinkles: Things to Consider
- relocatable packages
- Making relocatable packages with JHBuild - this discusses search/replace hacks, and talks specifically about how nix does it with their /nix/store/...<hash>... paths.