%% Regarding Use of vpath to build objects in separate directories;
%% Brian Appel <[EMAIL PROTECTED]> writes:
ba> I know vpath can be used to cause object files to be written to a
ba> directory tree separate from the original source.
No, it can't.
ba> In fact, if I run configure in my se
Hi. I'm a beginning autoconf/automake user.
I know vpath can be used to cause object files to be written to a directory
tree separate from the original source.
In fact, if I run configure in my separate destination directory, it builds
Makefiles there and I can perform the make there. However,
¾È³çÇϼ¼¿ä. »çÀü¿¡ Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»°Ô µÇ¾î Á˼ÛÇÕ´Ï´Ù. ¸ÞÀÏ ÁÖ¼Ò´Â ÀÎÅÍ³Ý °Ô½ÃÆÇ, ¹æ¸í·Ï µî¿¡ ¿Ã¸° ±Û¿¡ Ç¥½ÃµÈ °Í°ú
ÀÎÅÍ³Ý»ó¿¡ °ø°³µÈ °Í µîÀ» ¹«ÀÛÀ§·Î ¸ðÀº °ÍÀ¸·Î °³ÀÎÁ¤º¸ ħÇØ¿Í´Â ¹«°üÇÕ´Ï´Ù.°Ç°°ü¸®¿¡ À¯¿ëÇÑ Á¤º¸¸¦ Àü´ÞÇϱâ À§ÇÑ ¸ñÀûÀ¸·Î ¹ß¼ÛµÈ
°ÍÀÔ´Ï´Ù.
¼öµ¶¸¦ »¡¾Æ¸Ô´Â - ¼ö¾×½
Ok, being within LessTif again.
Trying to use the --force-missing flag I get a warning which doesn't
seem to be correct.
mai@crunch:~/compile/lesstif/lesstif/test > touch ltmain.sh
mai@crunch:~/compile/lesstif/lesstif/test > automake --add-missing --copy
--force-missing
--foreign --ignore-deps
On Tue, Sep 11, 2001 at 05:40:54AM +0200, Ralf Corsepius wrote:
> On Mon, 2001-09-10 at 23:31, Alexander Mai wrote:
> > Hello,
> >
> > I built a package using autoconf 2.13 and automake 1.5.
> >
> > AC_PROG_YACC
> > AM_PROG_LEX
> > are part of configure.in and we have .l and .y sources as well.