Cannot figure out how to call qualified rule about build

[grisumbras]

Figured out the source of the problem. I should have imported the module. This is missing from documentation, though. I can provide a patch.

[vprus]

Yep, patch or pull request for docs will be helpful.

Thanks,

On Пт, 20 марта 2015 at 21:07 Dmitry [email protected] wrote:

Figured out the source of the problem. I should have imported the module.
This is missing from documentation, though. I can provide a patch.

—
Reply to this email directly or view it on GitHub
#65 (comment).

[grisumbras]

It turns out, using just plain import my_module ; does not work. It does allow invocation of rules from the module, but it also tries to load my_module.jam. I did not notice that at first, because I created my_module.jam while I tried to solve the problem. So, loading fails (with an error message) without the file, but everything else works, due to IMPORT_MODULE builtin rule used in import implementation. In the end, I tried IMPORT_MODULE my_module ; and it works, but IMPORT_MODULE is not documented (as far as I see).

So, I think IMPORT_MODULE should also be documented.

[swatanabe]

AMDG

On 03/20/2015 03:06 PM, Dmitry wrote:

It turns out, using just plain import my_module ; does not work. It does allow invocation of rules from the module, but it also tries to load my_module.jam. I did not notice that at first, because I created my_module.jam while I tried to solve the problem. So, loading fails (with an error message) without the file, but everything else works, due to IMPORT_MODULE builtin rule used in import implementation. In the end, I tried IMPORT_MODULE my_module ; and it works, but IMPORT_MODULE is not documented (as far as I see).

So, I think IMPORT_MODULE should also be documented.

Agreed, but you should generally use import with
a separate file instead of using "module" directly.

In Christ,
Steven Watanabe

[grisumbras]

I understand that. My point was that an example from the official manual does not work. I think that incomplete (and as it turns out even incorrect in some places) documentation is the largest problem of Boost.Build. Maybe maintainers could provide me with a guideline on what parts of documentation need contribution the most?
P.S. PR for this particular issue is on way.