[Top][All Lists]

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

[Q] Absent directories and automake

From: zaufi
Subject: [Q] Absent directories and automake
Date: Sat, 3 Jan 2004 06:23:43 +0300
User-agent: KMail/1.5.94

Hi all!

I have little 'strange' (from automake's point of view :) configuration:
in my CVS there is 2 modules present: mylib and mylib-tests -- 2nd is 
interested for developers (of mylib) only, while mylib is available for 
public (usual users) by `cvs co mylib` command. Developers of mylib may 
checkout mylib and tests at once by `cvs co mylib-devel` where is mylib-devel 
is a special CVS module to checkout both modules: mylib module into 'mylib' 
directory and mylib-tests into 'mylib/tests' directory. So directory 
$(top_srcdir)/tests present only in "developer's checkouts"...

In my configure script I have the following:

 #... snip ...
 if test "x$USE_MAINTAINER_MODE" = "xyes"; then
     tests/Makefile \

and in top level

      SUBDIRS += tests

+ and some other tricks dependend on USE_MAINTAINER_MODE and MAINTAINER_MODE 
condition in

BUT the problem is: for usual checkouts (when no tests/ directory appear after 
checkout) my bootstrap script fails on automake execution with following: required directory ./tests does not exist

Is there is any way to avoid this behaviour of automake? If no, maybe it is 
reasonable to allow user to control what files maybe absent and prevent (by 
some automake option) to issue an error? I found that such configuration is 
quite suitable for my project but currently I can't implement it :(((
Any objections why it can't be implemented (suppressed)??


reply via email to

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