Hi Michael, and All,
> In my work-in-progress Debianization of klee [1], I encountered the same > need > you did and adopted a very similar KLEE_LIB_DIR configuration point. > However, > as you can see in the relevant patch [2], I also found it convenient to > use the > resulting KLEE_LIB_DIR definition as a default value for a new > "--klee-lib-dir" > interpreter command-line option. > > The advantage that I see in adding a runtime configuration-point like a > command-line option is that it lets me write tests directly against the > klee > binaries and libraries in their build-tree locations while still > permitting the > same binaries and libraries to function in their installed locations > without > modification. > > Might a strategy like this one work for you too? > > Regards, > > Michael > > [1]: https://github.com/mstone/**klee/ <https://github.com/mstone/klee/> > [2]: https://github.com/mstone/**klee/commit/** > a817cbb5e96917813cfbdfbd6c31d1**7a5b52162b<https://github.com/mstone/klee/commit/a817cbb5e96917813cfbdfbd6c31d17a5b52162b> > > > I really like that change. And as the default is the installed lib dir that would be perfect for me, and the added flexibility is a good idea. But it does afaik change the default behaviour of klee which everyone else might find an unpleasant surprise, i.e. we're supposed to always install klee before it can be used (in default settings) now. Not bad, just a change everyone should then know about..
_______________________________________________ klee-dev mailing list [email protected] http://keeda.Stanford.EDU/mailman/listinfo/klee-dev
