Andrew V. Teylu
Andrew V. Teylu
@selwin any thoughts on the best way to start this?
Okay, I can take a look at this!
Yeah, maybe you're right ... my concern is that we don't actually have CI until that branch is in (given Travis is gone).
> there is in most cases not much of an improvement, in some cases performance even decreases (expand, expr, nl). > So overall worse? > Another observation is that STP...
What's the easiest way for me to reproduce these myself? Build KLEE against STP's master and run a certain test?
@conp-solutions sorry if this is a silly question, but why are the Riss and MergeSat back-ends only compiled statically? We recently disabled static builds through Travis (as they didn't work)....
@conp-solutions do you think we can split off https://github.com/stp/stp/pull/354/commits/8e4ff44e5bb3dac529b916918590b797721c9680 into a separate PR? I don't think you need this for this branch (as it seems this branch *only* has `#define...
@carlocab after doing the install and the packages going into `PYTHON_LIB_INSTALL_DIR`, where is `libstp.dylib`? How does `library_path.py` look? Reasonable? I'm not suggesting it is broken, I'm just checking that things...
Ha, yeah, just because `cmake` puts it in `${CMAKE_INSTALL_PREFIX}/lib` doesn't mean that's where `library_path.py` looks for it: ``` @CMAKE_LIBRARY_OUTPUT_DIRECTORY@/@LIBSTP_FILENAME@ ``` Anyway, does `brew` install it to somewhere that's on `DYLD_LIBRARY_PATH`?
Hmm, so, just so I understand: on some platforms, the above check fails and then we `rpath` the STP libs to be `lib64` (like it is relative path), when actually...