>
> subversion/tests/libsvn_subr/.libs/lt-stream-test ? I dont see that.
>
> shell wrapper?
libtool has the shell wrapper trick, which makes sure that correct
version of libs are getting loaded by the program that is getting wrapped.
This shell wrapper sets the LD_LIBRARY_PATH and such to the relevant
libraries(in this case libs from your build area) and starts the wrapped
program.
Each build dir should have '.libs' directory, Not sure why you could not
see them, do 'ls -al'.
>
> I understand that compilation of these tests are a little different
> because the tests themselves are of a particular format, while the
> main() resides in subversion/tests/svn_test_main.c. But I do not
> really understand the intricacies. Could you pl. explain if you do
> understand them? thanks.
Don't bother about main sitting somewhere else.
For the framework svn_test_main.c is not going to be linked
independently by itself, rather svn_test_main.o is getting linked
individually to each 'C' test. For all practical purposes each 'C' test
program as its own statically linked 'main' method.
>
> Regards,
> Madan.
>
>
>>> PS : Contents below are for my personal patch management. Pl. do not
>>> remove the below text while replying to this mail.
>>> MY-SVK-TAG: helpfortests
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 30 13:37:41 2006