On 09/07/2016 02:42 AM, Bent Bisballe Nyeng wrote: > Hi list > > I have a project in which I include a few out-of-tree cpp files in one > of my SOURCES directives. > > I am currently trying to use the new subdir-objects argument but am > having the problem that autoconf tries to write a .deps folder to the > folder containing the out-of-tree files which is located in a system > folder and therefore not writable to the user. > > Is it possible to somehow force autoconf to write this .deps folder in a > location inside the project tree? Creation of .deps folders is done by automake, not autoconf. You may get a better answer from the automake lists. However, having out-of-tree files as part of your project seems fishy; as I understand it, automake works under the assumption that every cpp file being compiled is part of the distribution tarball, so that the build is reproducible (someone unpacking your tarball on their system would otherwise have to guarantee they have the same out-of-tree cpp files as you were building with). > Or can I perhaps resolve my issue in another way? > (I would really like avoid having to copy the out-of-tree cpp files to > an in-tree folder before compilation) But how are you making the tarball work, without those out-of-tree cpp files? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
