Building SHARED and STATIC library

[cinemast]

As I can see, it is currently not possible to build both versions, correct?

Would a PR that offers this functionality be merged? I want to package a more recent version for debian, which requires .a and .so version of it.

[cdunn2001]

Would a PR that offers this functionality be merged?

Yes.

But isn't it possible to build both as two separate cmake runs, in 2 different directories? We test each in Travis CI regularly.

I want to package a more recent version for debian

Hopefully 1.4.x, at least.

[cinemast]

Yes, but it is not the common practice, and makes the packaging more complicated without benefits.

I will start with 0.7.1 for sid, and maybe build 1.4 for experimental. It depends on your ABI/API compatibility. Do you check them somewhere?

[cdunn2001]

The whole point of 1.x is to drop the old ABI compatibility. If you need that, then you still need 0.7.x.

[cdunn2001]

I'll try to include some of the recent, minor fixes into 0.8.0, still ABI compatible.

[cinemast]

That would be great. 👍

[cinemast]

Could you wait with releasing 0.8.0 until I completed the pullrequest for building shared and static lib together?

[cdunn2001]

No problem. Actually, 0.8.0 will be rebased near the tip of master anyway. I'll integrate your changes there too.

Will you be able to double-check ABI compatibility? If not, I'll just build our test with old and link with new.

[cinemast]

You might tell Andrey that the project has moved: http://upstream.rosalinux.ru/versions/jsoncpp.html

[cinemast]

But aside of that, of course I can check ABI compatibility. In fact I have to if this package should really be going on the debian archives.

[cdunn2001]

You might tell Andrey that the project has moved: http://upstream.rosalinux.ru/versions/jsoncpp.html

That only lists his linkedin account. Can you connect us? I'm @cdunn2001.

[cinemast]

http://upstream.rosalinux.ru/

Just click on the add link on the top of the list.

I don't care about linkedIn, sorry.

[cinemast]

API compliance does not look too good.

https://gist.github.com/cinemast/35a7362d9bcbd4c92f7f

result: INCOMPATIBLE (Binary: 62.3%, Source: 0.1%)
total "Binary" compatibility problems: 6, warnings: 7
total "Source" compatibility problems: 2, warnings: 7

Do you think you can fix that?