Re: update libjson

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 does install_name_tool to 
change install_name again. Can the makefile just do it correctly right 
away?

dan

On Sun, 18 May 2014 17:28:44 -0400, Jack Howarth 
<[email protected]> wrote:
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. 
>                  Jack
>
> On Sat, May 17, 2014 at 1:57 PM, Daniel Macks <[email protected]> wrote:
>
>       On Sat, 17 May 2014 13:07:14 -0400, Jack Howarth 
> <[email protected]> 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. This upgrade to the newer libjson 
> release allows the package to be built against clang++ instead of 
> llvm-gcc++ which doesn't exist on 10.9.  Build-fails for me on 10.8. 
> But succeeded if I re-added UseMaxBuildJobs:false that is present in 
> the current .info. Is there value in still having the static lib now 
> that there is a shared one?
>
> There are two "libjson" library packages (this one and "json-c"), and 
> now both will have shared (they should probabaly Conflicts/Replaces 
> not just Conflicts). They also use the same install_name root 
> ("libjson"). For now, they have different library-versioning 
> (libjson.0.dylib bs libjson.7.dylib), but they are two independent 
> projects. I wonder if one (I guess this new one, since it doesn't 
> already exist in fink) should be pushed into a subdir to avoid any 
> future collisions of the runtime files?
>
> dan
>
>  --
> Daniel Macks
> [email protected]
>
> -------------------------
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. 
> Get unparalleled scalability from the best Selenium testing platform 
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs -------------------------
>
> _______________________________________________
> Fink-devel mailing list
> [email protected]
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.devel
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-devel
>

  --
Daniel Macks
[email protected]



------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel