Update of bug #25011 (project gnustep):
Status: None => In Progress
_______________________________________________________
Follow-up Comment #2:
Analyzed ... on windows we use relative paths rather than absolute ones, so
that we can find the paths to various resources wherever the gnustep
installation is moved to.
However ... the paths are calculated relative to the base library at
configure time, so if the base library is not installed tin the assumed
location within our path hierarchy, some paths are wrong.
Workarounds ...
1. install base library into the system domain and delete any copy in the
local domain
2. provide a GNUstep.conf specifying the paths (overriding the hard-coded
ones)
Proper solution ... allow the eventual installation domain to be specified at
configure time, and have the installation process detect any conflict between
the configured installation domain and the actual installation domain, and
reconfigure/rebuild if necessary.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25011>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
