On Thu, 2003-10-23 at 21:51, Guillaume Laurent wrote: > On Thursday 23 October 2003 15:39, John Anderson wrote: > > > > Hmm. Shouldn't PKG_CONFIG_PATH be set appropriately in one of the > > /etc/profile scripts if something's been installed in /usr/local? > > No. /etc/profile stuff is shell-specific, something installing in /usr/local > will never touch it. Or if you mean that one should manually set that var in > whatever /etc/profile script is appropriate, may be, but that's not something > we can rely on.
Would it be fair to assume that someone who installs something like jack in a non-standard location could also be expected to figure out how to set an environment variable? > > can take an action for package not found might be complicating things. > > The default is to stop the configure and complain that jack.pc couldn't > > be found in PKG_CONFIG_PATH. But jack isn't a requirement for rosegarden > > to compile, so that behaviour is inappropriate. > > It should simply set a var indicating jack couldn't be found. > > > What would be the right thing to do? Have a message at the summary at > > the end of configure say why jack support isn't compiled in? > > Yes. > > > But I'm not > > sure that there's a way to retrive the "jack.pc not found" message. > > There must be, if only because pkg-config returns a non zero value. I did a bit of digging. It looks like the pkg.m4 script sets a var called JACK_PKG_ERRORS. bye John ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
