On Tuesday 17 January 2006 13:27, Ralf Wildenhues wrote:
> Have you ever done a VPATH build?
> mkdir build
> cd build
> ../qdvi/configure [...]
> make
Hi, Ralf.
Yes, I do exactly this already. On a Linux machine the invocation I use is:
==
On Sun, 2006-01-15 at 21:21 +, Angus Leeming wrote:
> Guys,
>
> I'm having difficulty with the following set of files and compilation
> requirements.
>
>qdvi/
>psheaders.txt \
>squeeze.c \
>psgs.cpp \
>psgs.h
>
> 1 squeeze.c it to be c
Hi Angus,
* Angus Leeming wrote on Tue, Jan 17, 2006 at 11:10:01AM CET:
>
> Making all in qdvi
> make[2]: Entering directory
> `/home/angus/qdvi/trunk/build/qdvi-4.0cvs/_build/qdvi'
> if cmp -s version.cpp-tmp version.cpp ; then \
> : ;\
> else \
> rm -f version.cpp ;\
> c
Harlan Stenn wrote:
> What about DIST_SUBDIRS?
Nice idea, but no.
Angus
Making all in qdvi
make[2]: Entering directory
`/home/angus/qdvi/trunk/build/qdvi-4.0cvs/_build/qdvi'
if cmp -s version.cpp-tmp version.cpp ; then \
: ;\
else \
rm -f version.cpp ;\
cp version.cpp-tmp
What about DIST_SUBDIRS?
h
Angus Leeming wrote:
> ...Late press: I have a solution! Not sure how pretty this is, but it
> does work.
Actually, it *almost* works. "make distcheck" on a clean build tree fails
becase distcheck seems to ignore the subdirs order. If I "make" before I
"make distcheck" then distcheck succeeeds bec
Harlan Stenn wrote:
>> Unfortunately, going this route will mean my project loses all CVS
>> history information :( If only sourceforge were using subversion. (Yes,
>> I know they plan to do so "real soon now".)
>
> Ah. Can you copy the ,v files to the new dir and then cvs rm the old
> ones?
No
> > If kconfig_compiler needs any prebuilt stuff, then for the first
> > bootstrap you are gonna need to manually create things and have them in
> > the repo.
>
> Sorry, you've lost me. What do you mean by "prebuilt stuff"?
The files you generate.
> > If it doesn't need it, I suspect the easiest
Harlan Stenn wrote:
> If kconfig_compiler needs any prebuilt stuff, then for the first
> bootstrap you are gonna need to manually create things and have them in
> the repo.
Sorry, you've lost me. What do you mean by "prebuilt stuff"?
> If it doesn't need it, I suspect the easiest way to go will
If kconfig_compiler needs any prebuilt stuff, then for the first
bootstrap you are gonna need to manually create things and have them in
the repo.
If it doesn't need it, I suspect the easiest way to go will be to
reorganize a bit so you build everything out of subdirs (nothing in the
top-level dir
Harlan Stenn wrote:
> If you have:
> SUBDIRS= subdirs
> that really means:
> SUBDIRS= . subdirs
> Try:
> SUBDIRS= subdirs .
> instead.
Thanks, but I have the right form. In fact, Makefile.am attached. The
resulting output from make is:
$ make
make[1]: Entering directory `/home/angus/qdvi/trun
If you have:
SUBDIRS= subdirs
that really means:
SUBDIRS= . subdirs
Try:
SUBDIRS= subdirs .
instead.
H
Harlan Stenn wrote:
> Try reading the docs about BUILT_SOURCES.
Thanks. I'll do that again. However, I have a related problem that I
couldn't resolve with BUILT_SOURCES, so bear with me:
If I modify my structure to:
qdvi/
subdir/
foo.cpp
bar.txt
such that
1 sub
Try reading the docs about BUILT_SOURCES.
H
Guys,
I'm having difficulty with the following set of files and compilation
requirements.
qdvi/
psheaders.txt \
squeeze.c \
psgs.cpp \
psgs.h
1 squeeze.c it to be compiled to create an executable squeeze.exe.
2 squeeze.exe is used to generate pshe
15 matches
Mail list logo
