skaller <[EMAIL PROTECTED]> (on Thu, 01 Feb 2007 12:02:02 +1100): > On Wed, 2007-01-31 at 23:53 +0100, Jens Peter Secher wrote: > > On 1/30/07, Nicolas Cannasse <[EMAIL PROTECTED]> wrote: > > > pkg-config is a Debian thing. It provides the right include path and compile > > flags. > > No, yes. pkg-config is a *Red Hat* thing and it is frowned on by Debian. > [As it should be, it's a heap of crap].
Yes, No. pkg-config is (mostly) a *Havoc Pennington* thing, and a *freedesktop.org* project. I oppose the idea that it's a heap of crap ;). I find it one of the most useful tools around C development. Before, many libraries would install a "foo-config" script to achieve the same. pkg-config standardized that. On my laptop's gentoo, there are 429 pkg-config files, from openssl via glib to X-- i think that classifies it as "widely used". In fact, i would opt for neko to install such a file for dependants to link against libneko. Good to see some linux people around, though. I'm all for a install option to link mysql.ndll dynamically-- static linking is frowned upon on gentoo, too, as it results in TEXTREL relocations. Obviously, assuring the correct version of dependencies is solved with the various package managers on linuxes. I've been wanting to propose something for assuring dependencies for neko-based haxelibs that link against external libraries, but haven't gotten around to trying/verifying it (yet). I'm thinking of a small tool (could be a haxelib) that interfaces to the local package manager (or provides some installation method on platforms without a package mgr). The tool would require metafiles for external libraries (much like the metafiles in .debs or .rpms), containing some URLs and a list of dependency libs. Then, * on Windows, it would fetch the project's public win32 binary .zip and unpack the DLLs to a haxe-specific LDPATH * on OSX, it would get the (x86 *or* ppc) fink package (a .deb) and do the same. * on linuxen, it *could* interface with the local package managers (although i'd like it to not require root privileges), or alternatively (or as a fallback) try to link a simple test against the specified lib and prompt the user to install the dependency manually (if it fails). Such a tool could well be thought as an extension to haxelib. It would enable haxelibs to resolve their dependencies in platform-specific ways (and avoid binary redistribution of things that are mostly already installed on linuxen, like GTK). What do you think, is that a good idea? Then, Nicolas, could we have an official source distribution for haXe? It's kind of essential to have for source-based package managers (like gentoo ebuilds). I disgress compiling from CVS (if it aint neccessary). -dan -- http://0xDF.com/ http://iterative.org/ -- Neko : One VM to run them all (http://nekovm.org)
