1 |
Supposing that you have those |
2 |
#provide header <header.h> |
3 |
lines in all your packages, which provide something (and, of course, only in |
4 |
those places in code, where they actually do so that useflags might be |
5 |
correct), there may be some command of dep builder, which just uses those |
6 |
providings, putting them together with it's |
7 |
#use header <header.h> |
8 |
|
9 |
This is not maybe common case, when interfaces and atoms have to be used. |
10 |
|
11 |
File with |
12 |
#provide header <header.h> |
13 |
lines could also be autobuilt -- if you have copied all common *.h files |
14 |
into some dir, which you are going to just put into /lib, then you're done. |
15 |
|
16 |
That's somewhat a question, how it should be differenciated if .so is needed |
17 |
or just headers and code, but there are several more or less simple |
18 |
solutions. In all cases, data about which .so file is needed should be |
19 |
contained in .h file, not in a package, which is going to use it -- i think |
20 |
so. |
21 |
|
22 |
2006/3/22, tvali <qtvali@×××××.com>: |
23 |
> |
24 |
> As an addition to code deps discussion. |
25 |
> |
26 |
> I didnt understand exactly, why bin deps were supposed to be better than |
27 |
> what we have now, as i am not yet exactly sure what we have :) |
28 |
> |
29 |
> Anyway, i see one basic plus of code deps. It's that you may have huge |
30 |
> number of codelines, all containing #defines and #ifdefs. You may know that |
31 |
> whenever it uses <?.h> header, it needs library ? -- but when you need <?.h> |
32 |
> may be somewhat complex case. There may be, for example, 40 different .h |
33 |
> files of your own, which include ?.h file -- and each of them may be |
34 |
> included only if corresponding useflag is set. In such case, it's easier to |
35 |
> describe, which package you need when <?.h> is used than to write all those |
36 |
> if's twise in code and some other place, which make sure if you need that ? |
37 |
> pack or not. |
38 |
> |
39 |
> I havent done such thing in reality, so i dont know, how big problem it is |
40 |
> for a programmer (how much you have that situation i described in real |
41 |
> life), but i guess that this is the problem what binary deps were supposed |
42 |
> to solve. |
43 |
> |
44 |
> -- |
45 |
> tvali |
46 |
> |
47 |
> From a programmer's point of view, the user is a peripheral that types |
48 |
> when you issue a read request. -P. Williams |
49 |
> |
50 |
> If you think your management doesn't know what it's doing or that your |
51 |
> organisation turns out low-quality software crap that embarrasses you, then |
52 |
> leave. -Ed Yourdon |
53 |
> |
54 |
> We all agree on the necessity of compromise. We just can't agree on when |
55 |
> it's necessary to compromise. -Larry Wall |
56 |
> |
57 |
> [ http://www.softwarequotes.com/ ] - |
58 |
> http://www.softwarequotes.com/ShowQuotes.asp?ID=544&Name=Borenstein,_Nathaniel_S. |
59 |
> - http://www.softwarequotes.com/ShowQuotes.asp?ID=571&Name=Boehm,_Barry |
60 |
> |
61 |
|
62 |
|
63 |
|
64 |
-- |
65 |
tvali |
66 |
|
67 |
>From a programmer's point of view, the user is a peripheral that types when |
68 |
you issue a read request. -P. Williams |
69 |
|
70 |
If you think your management doesn't know what it's doing or that your |
71 |
organisation turns out low-quality software crap that embarrasses you, then |
72 |
leave. -Ed Yourdon |
73 |
|
74 |
We all agree on the necessity of compromise. We just can't agree on when |
75 |
it's necessary to compromise. -Larry Wall |
76 |
|
77 |
[ http://www.softwarequotes.com/ ] - |
78 |
http://www.softwarequotes.com/ShowQuotes.asp?ID=544&Name=Borenstein,_Nathaniel_S. |
79 |
- http://www.softwarequotes.com/ShowQuotes.asp?ID=571&Name=Boehm,_Barry |