[foo-devel] is a statically linked foo the solution?

[Gerhard E. <ec...@ie...>]

Dear Fooers,

last time I talked with Ramón, we thought it would be great to have a statically linked version of foo, which would install easily. I find it quite a pain that every time any component foo is dependent upon changes, we run into trouble building it (or even running it - at the moment I have a libsndfile with an mismatching architecture for my currentlty installed foo). If one masters the build system, then one is probably less frightened about this situation, because one can act in a situation of urgency. As I am not in this positions, it has happened several times in the last years, that I maneuver myself into a situation, where I break my installed version by upgrading to newer libs I need for other projects and only discover that I broke foo some time later, when I typically need it urgently (like now). Then I am stuck, as one tool needs the new libraries and the one the old ones. For this situation also and for installing foo quickly one somebody elses system (typically students' systems), I think a statically linked version would be very handy. Is this very difficult to realize? It would be great if one could specify this at build time.

Best regards,

Gerhard