Hi Gavin, Related to why the variable must be set, check this stack overflow article: http://superuser.com/questions/61185/why-do-i-get-files-like-foo-in-my-tarball-on-os-x
The Mac filesystem created a hidden file that causes problems when packaging a release. I guess, autotools should actually handle this by default, but currently it doesn’t yet. Right now, I just run a check. You can see what I’ve done at: https://github.com/cpputest/cpputest/blob/master/Makefile.am (line 344) This ensures I don’t forget to do it manually. I haven’t found a way to do it automatically yet ;( Thanks, Bas > On 10 May 2015, at 4:40 pm, Gavin Smith <gavinsmith0...@gmail.com> wrote: > > On 10 May 2015 at 13:57, Bas Vodde <b...@odd-e.com> wrote: >> I'm trying to change my projects configure.ac so that it sets the >> COPYFILE_DISABLE=1 environment variable to influence the make dist target. > > What running program needs to have this environment variable set in > its environment? Is it the shells that are created by Makefile rules > when make dist is run? > >> Background: The COPYFILE_DISABLE=1 avoids having a second top-level >> directory in your package when packaging on MacOSX. > > What programs pay attention to this variable? > >> So far, my attempt was to set the variable in the configure.ac file and use >> AC_SUBST on it, but that didn't seem to work. > > This will create a Makefile variable, which is different to an > environmental variable. That is, a line like "COPYFILE_DISABLE=1" will > appear in the generated Makefile, and this will be substituted > elsewhere in the Makefile if the COPYFILE_DISABLE variable is referred > to. However there is nothing there to change environmental variables.
