On 20/03/2013, at 11:33 PM, john skaller wrote:
> In order to get the new config stuff working I may have to break the build.
> Pls help to get it running again.
I had a another look at this an it's a bit ugly. At the moment the flx_pkgconfig
just points to
$FLX_INSTALL_DIR/config
and that's it. This works for the installed system, and for --test=build/release
or whatever from "flx" that changes the FLX_INSTALL_DIR and so the config
directory follows suit.
This means there's a 1-1 relation between a build and a config.
The only way to maintain user extensions is using
$HOME/.felix/config
during the build. This is not very flexible. To make a cross
compiler you have to make a complete new Felix.
However, the new concept requires propagating a
PKG_CONFIG_PATH
which is a list of config dirs (not necessarily via the above
environment variable: path lists can be sent by command
line switches too).
However there's a problem *identifying* this list and making
it persistent. The only sane way to do this is to put the path
list in a file with a filename....
... and then that file represents a particular config. And then
we have another problem: how to find the file. How to identify
the file.....
Until I can solve this in a nice simple way I think I have to back
off on changing the current system, lest we get caught up in
a tangle with everything broken and no clear design to find
the way out.
--
john skaller
skal...@users.sourceforge.net
http://felix-lang.org
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language
