|
From: Lorenzo B. <be...@ds...> - 2009-03-03 14:12:49
|
Earnie Boyd wrote: > Quoting Lorenzo Bettini <be...@ds...>: > >> the problem is configure script defaults $prefix to /usr/local. How can >> you make sure that any user downloads my program and by simply running >> configure it will build a working program, i.e., one where the hardcoded >> path works? This package builds a library, where the $prefix is >> hardcoded; how can this library use relative paths? It must start from >> a hardcoded one? >> > > The onus belongs to the executor of configure to follow the directions. > You can't guard against the idiots that don't follow the directions. mh... I don't think that's the case since we're talking about the default configuration... > > You determine the relative path based on the location of the executing > binary or dll. I do this for MSYS. GCC does it for finding its > libraries. Functions exist to return where the binary executes from. OK, any suggestion about this? I mean, how to find the location of the executing binary from with the program itself? And also for libraries? thanks in advance Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com http://www.myspace.com/supertrouperabba BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net |