Re: [Texmacs-dev] Linking against one of multiple installed libraries

[Miguel de Benito Delgado]

Hi Massimiliano,

On 13 Oct, 2013, at 22:29, Massimiliano Gubinelli <address@hidden> wrote:

> 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. 

I will try it.

> By similar reasons in my opinion this should be the way things have to be 
> done on Windows too.

Isn't this more or less the case? Albeit less elegantly, because the whole 
development environment is a zip instead of scripts to download and compile 
oneself...

> 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. 

Well, now that we are lagging almost 3 years behind the release of Guile 2, 
most users will have to install an older guile than the default one in the 
distro… but this is off the point.

> 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…).

Good point. I was actually thinking about changing the configure to do 
precisely that so I'm happy you told me this before. d'oh!

> 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.

Seems so, yes (but it'd still be nice to have a functioning configure script, 
meaning one which actually uses the libraries it's told to. And any library may 
be bundled within the .app package…).

Anyway, I'll try the tm-devel thing when I have time. You are quite right in 
everything you say and I appreciate the effort put into the tm-devel stuff.

Cheers,
--
Miguel.