Use noinst_SCRIPTS for toplevel audacity script.

[0-wiz-0]

When using libtool, this file is a copy of a shell script
and will be installed instead of the real executable.

[ferdnyc]

bin_SCRIPTS was changed to bin_PROGRAMS in commit 8d82270 (hence the conflict) — that seems correct, as the file in question was never a script. It's a copy of the compiled executable:

audacity$(EXEEXT): src/audacity$(EXEEXT)
	rm -f audacity$(EXEEXT)
	cp src/audacity$(EXEEXT) audacity$(EXEEXT)
	[ -e plug-ins ] || ln -s $(srcdir)/plug-ins
	[ -e nyquist ] || ln -s $(srcdir)/nyquist
	[ -e locale ] || ln -s po locale

So, with that executable correctly categorized as bin_PROGRAMS, I believe this can be closed as superseded by that change, no? I don't see that we'd want the executable to be noinst.

[0-wiz-0]

My original point is still valid.
When building on Unix with libtool, src/audacity$(EXEEXT) is a shell wrapper that sets the library search path before calling the real executable. libtool --install ... then creates the actual binary.
The target in the main Makefile.am runs too early and copies the shell wrapper, which points to the build path.

[JamesCrook]

Sorry, this has sat in the queue too long and is now being closed as we couldn't decide on progressing it.