25 Apr
2016
25 Apr
'16
3:15 p.m.
In article <nfi6e4$c7s$1(a)ger.gmane.org>rg>,
deloptes <trinity-devel(a)lists.pearsoncomputing.net> wrote:
Fat-Zer wrote:
You could perhaps set the LD_LIBRARY_PATH environment variable to point
to your test libraries and run an existing program against them.
The Linux loader ld.so searches directories named in LD_LIBRARY_PATH
before falling back to the system library directories. For instance
LD_LIBRARY_PATH=/path/to/libs/ kaddressbook
See "man ld.so" for full details.
Nick
--
"The Internet, a sort of ersatz counterfeit of real life"
-- Janet Street-Porter, BBC2, 19th March 1996
The testing framework wasn't introduced with
migration to cmake. I
believe that autotools unittests are broken as well now...
IMHO it would be great to bring unittesting back, but this is a bit
tough tasks which will be likely postponed forever... I personally not
familiar with cmake testing in general...
Thanks for looking into my issues
Is there a way in your opinion how we can test the vcardparser?
I was thinking overwriting the library files, but I'm not sure if the
libtdeabc.so.1.2.0 is the only one I should overwrite and if I have to
restart or reboot or whatever