Am Montag, 18. Dezember 2006 04:50 schrieb chromatic via RT: > On Mon May 09 07:36:14 2005, leo wrote: > > If you are embedding or extending Parrot and linked against libparrot > > you now have to additionally link with one of: > > > > src/null_config.o > > src/parrot_config.o # prefix := build-dir > > src/install_config.o # prefix := --prefix dir > > I wish I'd known that earlier, but for people who install libparrot, can > we link those into the single shared library and offer some API to > access this configuration information? Alternately, is it workable to > encode it as constants in the installed headers somehow?
We tried hard several times to get rid of that, w/o any success. We wanted to have a path to the config/lib/whatever-add-on-files-for-parrot inside parrot itself, so that any parrot executables will know to look for that stuff. An installed and an uninstalled parrot have different library paths ... The only scheme we got working is to link with an object file having that path inside. The extra config info also linked in is just some bonus but not needed. leo
