Makes sense. As long as it's done at the same time as a change of
install_name is happening for other reasons (new libversion), moving
the existing one to a subdir also will not be disruptive.
Unrelated new detail...your libjson.patch alters a makefile
-install_name flag and then libjson.info
Daniel,
FYI, the json-c package could stand an update as well since it is
behind by three releases…
https://github.com/json-c/json-c/wiki
so both packages could have their shared libs buried in subdirectories. As
for the static lib,
I built it as the the build is pretty quick.
Also, I wonder if we should really be distributing the internal headers for
this package.
On Saturday, May 17, 2014, Jack Howarth wrote:
> Daniel,
>I think we can also add an InfoTest. While 'make test' is broken in
> the top level make file, it appears to work if you do ' cd
> _internal
Daniel,
I think we can also add an InfoTest. While 'make test' is broken in
the top level make file, it appears to work if you do ' cd
_internals/TestSuite; make test; ./test all' which seems to also compile
the files in _internals/TestSuite2. I am still waiting for it to complete
because it
On Sat, 17 May 2014 13:07:14 -0400, Jack Howarth
wrote:
Sjors,
> The attached packaging updates the libjson to the latest
> 7.6.1 release and patches the makefile so that the fink build
> produces both the static and shared libs with the latter residing in
> a new libjson-shlibs split-off
Sjors,
The attached packaging updates the libjson to the latest 7.6.1 release
and patches the makefile so that the fink build produces both the static
and shared libs with the latter residing in a new libjson-shlibs split-off.
This upgrade to the newer libjson release allows the package to be
