| 1 |
On Thursday 23 March 2006 19:29, tvali wrote: |
| 2 |
> |
| 3 |
> In c++ code, use flags must definitely have something to do with |
| 4 |
> #defines. Otherwise they couldnt do what they do -- so |
| 5 |
> uflags=>buildsys=>defines. |
| 6 |
> |
| 7 |
> Configure, for example, will define set of #defines. |
| 8 |
> |
| 9 |
> Ok, your answer at least shows that this relation is not as simple and |
| 10 |
> clear as i would like it :) |
| 11 |
> |
| 12 |
> Where i could see some useflag actually interacting with build? Where |
| 13 |
> i see that line which makes it so that if i define "gtk", gtk support |
| 14 |
> will be added to makefile? |
| 15 |
|
| 16 |
The semantics that make up the relationships between useflags and the actual |
| 17 |
source as goes out of the preprocessor is very complicated. Probably the |
| 18 |
easiest way to find it out is to try each permutation and somehow hook into |
| 19 |
gcc/g++ to get the result of that choice. |
| 20 |
|
| 21 |
And that's only for C and C++ sources. |
| 22 |
|
| 23 |
Paul |
| 24 |
|
| 25 |
-- |
| 26 |
Paul de Vrieze |
| 27 |
Gentoo Developer |
| 28 |
Mail: pauldv@g.o |
| 29 |
Homepage: http://www.devrieze.net |
Archives