[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
a couple more questions on (what else?) multi-arch builds
From: |
Robert P. J. Day |
Subject: |
a couple more questions on (what else?) multi-arch builds |
Date: |
Fri, 12 May 2006 16:01:56 -0400 (EDT) |
just to start tying up some loose ends WRT multi-arch builds, part
of my goal is to extend some existing makefiles to fit into a
multi-arch build with as little modification as possible, so i have to
take into account two things:
1) that the existing makefiles might be "include"ing other files
2) that the C source files might be "#include"ing header files.
to handle that, i'm considering the following in the eventual
multi-arch support makefile:
CPPFLAGS += -I${CURDIR}
...
${MAKE} \
-C $@ \
--no-print-directory \
-f ${CURDIR}/Makefile \
SRCDIR="${CURDIR}" \
-I${CURDIR} \
CPPFLAGS="${CPPFLAGS}" \
${MAKECMDGOALS}
the appending to CPPFLAGS would handle C files including relative
header files, while the "-I${CURDIR}" would obviously deal with the
original makefile trying to include other files using a relative
pathname.
i haven't tested this yet, but does it make a minimal amount of
sense?
rday
p.s. obviously, if the original makefiles or C source files are
including things based on absolute pathnames, then it doesn't matter.
but chances are, there are going to be some relative path references
in there somewhere and i figure this is the easiest way to handle
them.
- a couple more questions on (what else?) multi-arch builds,
Robert P. J. Day <=