info-cvs
[Top][All Lists]
Advanced

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

Re: modules file


From: Kaz Kylheku
Subject: Re: modules file
Date: Fri, 05 Oct 2001 15:27:44 GMT
User-agent: slrn/0.9.6.3 (Linux)

In article <address@hidden>, Jeff Rancier wrote:
>Hello,
>
>All the references I have seen so far regarding the modules file, refer to
>the *global* one, in $CVSROOT, and appear to alias a name to a single
>(sub)directory.  E.g.

A modules file can contain two kinds of module definitions. Alias
definitions created using -a, and regular definitions.
Regular definitions can also use the ampersand syntax to express
module composition.

>(1) Can I maintain a local modules file?  I am using Windows, so do I make a

No.

>(2) I have multiple projects which share common C libraries and header
>files.  What would my my modules entry look like?

You should share entire directories, not files. A module entry can pick
individual files from a directory, as in:

        foo mylib foo.c foo.h

Module foo checks out ``mylib'' under the name ``foo'', but instead
of getting everything in mylib, it gets only the files mylib/foo.c
and mylib/foo.h.

Define your libraries as individual modules and then compose them
together:

        my_great_browser browser_root &xml_lib &html_lib &image_lib ...


reply via email to

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