No option to disable json-c lookup by ./configure

[mloskot]

./configure provides only one option to control searching of json-c library files:

$ ./configure --help|grep json
  --with-jsondir=PATH     specify the json-c installation directory

Assuming json-c is optional, unlike PROJ.4 library, if one wants to build PostGIS without json-c support on a system with json-c library installed, then the ./configure always detects and adds json-c support.

There is no option like —without-jsonc or —disable-jsonc.

[mloskot]

Patch that refactors json-c lookup to support —without option. It also implements Sandro's suggestion to rename the option to reflect json-c library name.

[strk]

A vanilla ./configure bails out: configure: error: Cannot find json dev files in ""

It works fine without the patch

[mloskot]

This error is not making the json-c optional.

Currently, if I have json-c installed and I do not want to enable json-c support, the only way to achieve it is to uninstall json-c.

[strk]

change in configure name goes to 2.1.0. If you come up with a working patch I'll apply. By working I mean that no switch enables it if available, —without disables it without complaining and —with complains if not found or uses from given path if found

[mloskot]

Sandro, does any of the other switches for 3rd-party deps work the same way? Which one? So I will follow the patter exactly.

[strk]

I'm afraid none of the other switches work the way I described above. Taking a look at this now.

[strk]

In r11144 (trunk) I added —without-json — the existing switch remained. See how you like it.

[mloskot]

Replying to strk:

I'm afraid none of the other switches work the way I described above. Taking a look at this now.

Sandro, yes, that's what confused me. Thanks for fixing it anyway.

[strk]

mloskot: tested ? can we close this ?

[mloskot]

Works for me.