|
From: | Massimiliano Gubinelli |
Subject: | Re: [Texmacs-dev] Linking against one of multiple installed libraries |
Date: | Sun, 13 Oct 2013 22:29:24 +0200 |
Miguel, these kind of problems made me lose a lot of time. On Mac I think the correct strategy is not to rely on ANY preinstalled library and make his own local developement environment. Recompiling all the libraries needed by TeXmacs can take at most half an hour on a modern machine and saves a lot of time fighting with incompatible versioning. I've set up a complete developement environment in misc/tm-devel-mac with packages for all the software needed by texmacs. There is a configure-tm file which can be easily hacked to call configure with all the right paths and dependencies once the environment is set up. I can have the control on the Qt flags and have guile linked statically in the source. In any case system libraries are a no opt if you are creating a bundle and you want it to be robust. By similar reasons in my opinion this should be the way things have to be done on Windows too. For Unix machines one should rely on system libraries so have two versions of the same library installed should be considered not the common thing. An option of course can also be to change all the configure to allow for exact paths of libraries but this will not solve the problem since you cannot ensure that a library which you call uses another copy of a library which you have linked in manually (for example think about guile and TeXmacs using different copies of gmp or libz, etc...). So I think the easiest way to have a complete control of libraries (on Mac and Windows) is to recompile them locally with strict control of the building environment. Best, Max On Oct 13, 2013, at 10:13 PM, Miguel de Benito Delgado <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |