Mike Frysinger , 2024-01-13 07:26:
On 21 Mar 2023 23:05, Bogdan wrote:
Third, and most important (I think) is that we need to note that
"prog/x.py" is GENERATED, but is NOT marked so. Adding
BUILT_SOURCES = prog/x.py
i don't think this is a correct use of BUILT_SOURCES.
https://www
On 21 Mar 2023 23:05, Bogdan wrote:
> Third, and most important (I think) is that we need to note that
> "prog/x.py" is GENERATED, but is NOT marked so. Adding
>
> BUILT_SOURCES = prog/x.py
i don't think this is a correct use of BUILT_SOURCES.
https://www.gnu.org/software/automake/manual
Hi all.
A small contribution to the discussion.
First of all, it's not an Automake defect that the user is allowed
to override variables using the command line. This may be used e.g.
for changing compile flags at 'make' time:
make CFLAGS=-Wall
Second, in the provided example, the
On Mon, 28 Mar 2011 09:36:45 +0200, A.T.Hofkamp wrote:
> As far as I know, "make install prefix=/path/to/writable/dir" should only
> change the place where
> files are copied to, instead of injecting that new prefix into the source
> code. However, for Python
> source files that are generated/m
Ralf Wildenhues wrote:
Looks like it. Can you work around this issue by adding
all-local: $(prog_PYTHON)
to the Makefile.am?
Confirmed that this addition fixes the problem for me, both with the 'p'
example and the real case.
Thanks for the quick fix.
Albert
Hello,
* A.T.Hofkamp wrote on Mon, Mar 28, 2011 at 09:36:45AM CEST:
> As far as I know, "make install prefix=/path/to/writable/dir" should
> only change the place where files are copied to, instead of
> injecting that new prefix into the source code. However, for Python
> source files that are gen
Hello,
As far as I know, "make install prefix=/path/to/writable/dir" should only change the place where
files are copied to, instead of injecting that new prefix into the source code. However, for Python
source files that are generated/modified during installation, this does not seem to hold:
