This is a port of Jansson 2.14 to MSDOS/DJGPP. Jansson is a C library for encoding, decoding and manipulating JSON data. 1.: DJGPP specific changes. ======================= - This port has been configured to be build in the "0build" directory. - The port has been configured and compiled on WinXP SP3 and Win98SE. There is absolute no guarantee that this may be possible with any other DOS-like OS. Due to the use of long file names it will not be possible to configure and compile without LFN support. - This version of the port has been compiled using gcc346 and bnu2351b. As usual, all djgpp specific files (config.bat, diffs, readme files, etc.) are located in the djgpp subdir. For further information about Jansson please read the info docs and NEWS file. 2.: Installing the binary package. ============================== 2.1.: Copy the binary distribution into the top DJGPP installation directory and unzip it running *ONE* of the following commands: unzip32 jsn214br2.zip or djtarx jsn214br2.zip or pkunzip -d jsn214br2.zip 3.: Building the binaries from sources. =================================== 3.1.: Create a temporary directory and copy the source package into the directory. If you download the source distribution from one of the DJGPP sites, just unzip it preserving the directory structure running *ONE* of the following commands: unzip32 jsn214sr2.zip or djtarx jsn214sr2.zip or pkunzip -d jsn214sr2.zip 3.2.: To build the binaries you will need the following binary packages: djdev205.zip (or a later but NOT a prior version) bsh205bbr3.zip (or a later but NOT a prior version) gccNNNb.zip, bnuNNNb.zip, makNNNb.zip, filNNNb.zip, shlNNNb.zip, txtNNNb.zip, txiNNNb.zip, grepNNNb.zip, sedNNNb.zip, mktmpNNb.zip and difNNNb.zip. NNN represents the latest version number of the binary packages. All this packages can be found in the /v2gnu directory of any ftp.delorie.com mirror. You will need bsh205bbr3.zip or later and *NOT* a prior version or the build will fail. The same applies to djdev205.zip. 3.3.: The package has been configured to be build in a separate build directory under the top srcdir (aka jansson-2.14). To build the binaries cd into "0build" directory. If for some reason you want to reconfigure the package cd into the build directory and run the following commands: del config.cache make clean ..\djgpp\config ./.. Please note that you *MUST* delete the config.cache file in the "0build" directory or you will not really reconfigure the sources because the configuration informations will be read from the cache file instead of being newly computed. config.bat, among other things, will start the configure script passing to it a couple of arguments. You can control these argument passing the following command line arguments to config.bat: cache or no-cache, default cache. Cache in build directory. dep or no-dep, default no-dep. No dependency tracking. silent or no-silent, default silent. Controls the verbosity of the build process. urandom or no-urandom, default urandom. /dev/urandom support enabled. All other configure specific options are not set by config.bat so their values are left as they are. If no arguments are passed to config.bat then the default values are used. Having urandom support enabled means that a entropy source must be available at runtime either as driver or as random data file. One such driver, NOISE.SYS, can be obtained from "http://www.rahul.net/dkaufman/index.html" as: http://www.rahul.net/dkaufman/noise063a2.zip If the URLs are no longer available, the the followings can be used: http://web.archive.org/web/20051124224824/http://www.rahul.net/dkaufman/ and: http://web.archive.org/web/20051124224824/http://www.rahul.net/dkaufman/noise063a2.zip Please read the instructions carefully. This driver works on DOS and may be on some versions of Windows but it does not work for all versions of Windows. For XP it does not work and I have found no replacement. Alternatively a random data file can be used. It will be found by the library by evaluating the RANDFILE environment variable. If neither a noise driver nor a random data file is found at run-time then the random data will be created by calling rand() using rawclock() to generate the required seed for srand(). To build the programs in a directory other than where the sources are, you must add the parameter that specifies the source directory, e.g: x:\src\contrib\jansson-2.14\djgpp\config x:/src/contrib/jansson-2.14 Lets assume you want to build the binaries in a directory placed on a different drive (z:\build in this case) from where the sources are, then you will run the following commands: z: md \build cd \build x:\src\contrib\jansson-2.14\djgpp\config x:/src/contrib/jansson-2.14 The order of the options and the srcdir option does not matter. You *MUST* use forward slashes to specify the source directory. The batch file will set same environment variables, make MSDOS specific modifications to the Makefile.in's and supply all other needed options to the configure script. 3.4.: To compile the package run from the directory where you have configured the sources the command: make 3.5.: Now you can run the tests if you like. From the directory where you have configured the sources run the command: make check 3.6.: To install the binary, info docs and man pages run the following command from the directory where you have configured the sources: make install This will install the products into your DJGPP installation tree given by the default prefix "/dev/env/DJDIR". If you prefer to install them into some other directory you will have to set prefix to the appropriate value: make install prefix=z:/some/other/place Send Jansson specific bug reports to . Send suggestions and bug reports concerning the DJGPP port to comp.os.msdos.djgpp or . Enjoy. Guerrero, Juan Manuel