--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2010-01-21 01:09:43 PST ---
(In reply to comment #1)
(In reply to comment #0)
> Either we need a better solution, or the nightly testing must use
> --enable-integration-tests. I'm not sure what the effects of that for the
> generated binary packages are, though.
> Congwu, ideas?
I got stuck here. I remember I disabled this:
171 # Always compile the registry files into client-test because that is
172 # the only place where they are compiled with
173 # ENABLE_INTEGRATION_TESTS. This works without undefined references
174 # because client-test is linked against all shared backend libraries
175 # (non-portable, but works).
176 # Disabled now, the client test can also be dynamically loaded and
177 # just the same as syncevolution
178 # if ENABLE_MODULES
179 # client_test_SOURCES += $(BACKEND_REGISTRIES)
180 # endif
So we either re-enable the un-portable build for client-test
"non-portable" isn't the problem (it works on our platforms). The main
is that backends developed by someone else and then plugged into SyncEvolution
at runtime won't have the necessary code in client-test.
Can we solve this problem perhaps by making test.h usable enough for
registering test in backends even when CPPUnit headers are not available?
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.