Concern about current swig includes dependency info generation

The current swig build uses a number of swig include files which are
generated, not shipped.

An unfortunate consequence of this is that the generated build-outputs.mk
contains *different* dependencies depending on whether gen-make.py has been
run before or after a "make swig-somelanguage".

If those dependencies are truly needed, they need to be generated before a
swig build has occurred, so that they make it into the build-outputs.mk
shipped in our release tarballs.

If those dependencies are not truly needed, they should not be output at
all, to avoid creating unnecessary differences between developers' working
copies and release builds.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 4 13:51:00 2005