[bind10-dev] unit tests and include symlink tree
Jelte Jansen
jelte at isc.org
Mon Feb 8 14:12:56 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeremy C. Reed wrote:
>
> I was going to remove include from the lcov report, but then realize it
> was inconsistent and the results would be wrong. I suggest we don't use
> the include symlink tree for the gtest tests.
>
just had a little chat on this on the room, but this might warrant a broader
discussion;
the 'simple' fix as proposed by Jeremy would move the cpp source files one
directory deeper; move src/lib/cc/cpp/* into src/lib/cc/cpp/cc/,
src/lib/config/cpp/* into src/lib/config/cpp/config/ etc.
Then we can use direct -I in make again and the include symlink tree shouldn't
be necessary for c++ anymore.
It is also equivalent to what we do in the python part; modules live under
src/lib/<module>/python/isc/<module>/
But i'm starting to wonder whether this whole setup is costing use more in terms
of inconvenience than it is worth for keeping code together for modules; if we
would lay it out as one source tree per language it would make so much things
cleaner (i.e. src/lib/cpp/<module> and src/lib/python/<module>). Then we also
wouldn't need the pyshared/ hack. And less path settings for build and
run-from-source.
I'll go run and hide now before one of you figures out how to throw a chair
across the ocean.
Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAktwG+gACgkQ4nZCKsdOncVmmgCfbyNfk7RvLYItizVl3VNnmTH8
aaQAoIR4bcWQqYEZCVKAdbcDQnb8fVde
=3sEd
-----END PGP SIGNATURE-----
More information about the bind10-dev
mailing list