[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Control of .deps folder generation location.

From: Eric Blake
Subject: Re: Control of .deps folder generation location.
Date: Wed, 7 Sep 2016 08:53:08 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

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

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]