nixpkgs/pkgs/development/tools/misc/ccls/wrapper

#! @shell@ -e

initString="--init={\"clang\":{\"extraArgs\": [@standard_library_includes@"

if [ "${NIX_CFLAGS_COMPILE}" != "" ]; then
  read -a cflags_array <<< ${NIX_CFLAGS_COMPILE}
  initString+=$(printf ', \"%s\"' "${cflags_array[@]}")
fi

initString+="]}}"

exec -a "$0" "@out@/bin/@wrapped@" "${initString}" "$@"
ccls: init at 0.20181225 - tested with [emacs](https://dl.thalheim.io/kdh-PwxzlwGKTEl1_NpTzg/2019-01-13-190156_1920x1080_scrot.png) and vim. - wrapped to pick up our cc wrapper environment -> works perfectly in nix-shell 2018-12-26 08:53:41 +00:00			`#! @shell@ -e`

			`initString="--init={\"clang\":{\"extraArgs\": [@standard_library_includes@"`

			`if [ "${NIX_CFLAGS_COMPILE}" != "" ]; then`
			`read -a cflags_array <<< ${NIX_CFLAGS_COMPILE}`
			`initString+=$(printf ', \"%s\"' "${cflags_array[@]}")`
			`fi`

			`initString+="]}}"`

makeWrapper: Remove unused extraFlagsArray feature There is a bug in this feature: It allows extra arguments to leak in from the environment. For example: $ export extraFlagsArray=date $ man ls Note that you get the man page for date rather than for ls. This happens because 'man' happens to use a wrapper (to add groff to its PATH). An attempt to fix this was made in 5ae18574fce in PR #19328 for issue #2537, but 1. That change didn't actually fix the problem because it addressed makeWrapper's environment during the build process, not the constructed wrapper script's environment after installation, and 2. That change was apparently accidentally lost when merged with 7ff6eec5fd8. Rather than trying to fix the bug again, we remove the extraFlagsArray feature, since it has never been used in the public repo in the ten years it has been available. wrapAclocal continues to use its own, separate flavor of extraFlagsArray in a more limited context. The analogous bug there was fixed in 4d7d10da6b1 in 2011. 2019-09-10 23:52:53 +01:00			`exec -a "$0" "@out@/bin/@wrapped@" "${initString}" "$@"`