search

secure-software-engineering / phasar

A LLVM-based static analysis framework.
Other
927 stars 140 forks source link

phasar installs files back into the directory next to the build directory #564

Closed yurivict closed 1 year ago

yurivict commented 1 year ago

List of files:

/usr/ports/devel/phasar/work/.config/phasar/DOTGraphConfig.json
/usr/ports/devel/phasar/work/.config/phasar/README.txt
/usr/ports/devel/phasar/work/.config/phasar/TaintConfigSchema.json
/usr/ports/devel/phasar/work/.config/phasar/glibc_function_list_v1-04.05.17.conf
/usr/ports/devel/phasar/work/.config/phasar/llvm_intrinsics_function_list_v1-04.05.17.conf
/usr/ports/devel/phasar/work/.config/phasar/phasar-source-sink-function.json
@dir /usr/ports/devel/phasar/work/.config/phasar
@dir /usr/ports/devel/phasar/work/.config
@dir /usr/ports/devel/phasar/work
@dir /usr/ports/devel/phasar
@dir /usr/ports/devel
@dir /usr/ports

/usr/ports/devel/phasar/work is the directory directory over the build directory.

Config files should be installed into a user-supplied directory so that packages would be able to install config files into $PREFIX/etc.

fabianbs96 commented 1 year ago

We install the configuration into "$(HOME)/.config/phasar". On most systems this is a reasonable choice, but you are right: This should be configurable