Yes, I did it. I tried to add the target both as SimpleTest and UnitTestLib.
Maybe Jam's cache is kept somewhere? Though, it shouldn't be.
20.03.2019, 20:46, Adrien Destugues <pulkomandy@xxxxxxxxxxxxx> Hi,
Sorry for the delay, I have been busy with other things...
- Not getting anything if you run a normal build is expected, unless you add
things to the image
- However, UnitTestLib adds your tests as a dependency of the unittests
target, so it should work there
- You need to add your subdirectory (crypto) to the jamfile in
src/tests/kits/, did you do that?
--
Adrien.
19 mars 2019 17:35 "Lee Mon" <strongleemon@xxxxxxxxxx> a écrit:
> But libnetapitest defines UnitTestLib this way.
> I also ran $JAM_EXEC -n -dm unittests but I wasn't able to find anything
related to cryptotest.
> Should I build some other target or should I somehow flush Jams cache?
> I use jam clean time to time.
>
>> 18.03.2019, 12:23, Stephan Aßmus superstippi@xxxxxx>
>> Hi Lee,
>>
>> Am 18.03.2019 um 00:14 schrieb Lee Mon:
>>> UnitTestLib libcryptotest.so :
>>
>> I am not sure, but this may setup a target named
>> "liblibcryptotest.so.so". And that's why your direct jam call does not
>> find it. Try naming it just "cryptotest". It is a convention that
>> libraries are named "lib*.so", so that is why the "UnitTestLib"
>> directive may add the prefix and suffix for you. Again, I am not sure
>> this is indeed what is happing, but maybe worth a quick try.
>>
>> Best regards,
>> -Stephan
