1 |
okay, this came up in a discussion today, and I figured it was time to |
2 |
mention something about it here: |
3 |
|
4 |
|
5 |
If your package, libFoo, installs .h files that directly require header |
6 |
files from libBar, then you have a Runtime dependency on libBar, not |
7 |
only a compile time dependency |
8 |
|
9 |
|
10 |
Why? Because libFoo should be usable at runtime, even for compiling |
11 |
things not managed by our tree. And if BazPack has a configure check, |
12 |
requires explicitly libFoo, tests for the presence of said header, and |
13 |
all checks out.. Then BazPack should be able to work, and libFoo's |
14 |
header certainly shouldn't be broken for use in compile. |
15 |
|
16 |
Runtime isn't only executables. |
17 |
|
18 |
|
19 |
//Spider |
20 |
|
21 |
-- |
22 |
begin .signature |
23 |
Tortured users / Laughing in pain |
24 |
See Microsoft KB Article Q265230 for more information. |
25 |
end |