Re: Some :include {once} weirdness
Adriaan de Groot <adridg-FlD2LfDziEhmR6Xm/[email protected]>
| Newsgroups | gmane.comp.tools.aap.user |
|---|---|
| Message-ID | <[email protected]> |
On Sunday 17 August 2003 16:52, Bram Moolenaar wrote:
> The main reason for using {once} is when you have a project that is
> split up in sub-projects. You would then include your project-global
> settings in the top project recipe and in each sub-project recipe. When
> building the whole thing and when building a sub-project the same
> settings are used. The {once} then avoids that the settings are loaded
> twice when building the whole project, once in the top recipe and again
> in the children.
The surprise here comes when you have two formerly independent projects with
recipes a/main.aap and b/main.aap. _If_ they include the same file for common
settings, and _if_ they do that with {once}, and _if_ that file sets
variables those recipes expect, _then_ (and only then) is creating a recipe
that compiles both projects more complicated than :child a/main.aap
b/main.aap. Adding a note to the documentation is probably the best way to
go.
--
pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <[email protected]>
Key fingerprint = 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01