On Wed, 2014-05-28 at 08:57 -0400, Darryl L. Pierce wrote: > On Tue, May 27, 2014 at 10:43:48AM -0400, Alan Conway wrote: > > On Fri, 2014-05-23 at 11:40 -0400, Justin Ross wrote: > > > In which scenarios are you having to set it? If you produce two builds to > > > two distinct install prefixes, they should be pre-defaulted with the > > > approprate home dir, so you shouldn't have to set it. > > > > If I do tests directly against a build rather than an install, I will > > pick up the installed version even if the build is first in PYTHONPATH. > > I can set QPID_DISPATCH_HOME in the build env script I just think it is > > ugly. I don't have a better solution (yet) given your point about not > > putting internals in site-config. > > Before you run the tests are you sourcing the config.sh file in the > dispatch repo directory? That should set up the environment for you to > run against that build. >
No, I'm sourcing build/tests/config-build.sh. The root config.sh assumes I want to test against an install in <root>/install. Usually I want to test against my build (which isn't in <root>/build, I tend to have different builds in debug and release directories) and install to /usr/local when I'm happy that it works. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
