Is there a "normal" way? Last time I checked, pretty much everyone builds TigerVNC differently. Your official build maintainer (Brian) is producing a cross-compatible build like I used to do, and this issue adversely affects the ability to do that. Thus, I would think that such a build qualifies as "normal", since it's necessary to build that way in order for anyone to reproduce your official binaries.
I would be more inclined to agree with your argument if the "official" version of FLTK included all of the necessary patches to build TigerVNC, and if FLTK were a more ubuitous framework found on most platforms. The reality is, though, that almost all people who want to build TigerVNC from source will be building FLTK from source as well. By making it this difficult, you are removing a lot of potential testers from your community. I also find your argument to be a bit hypocritical, since Cendio builds TigerVNC statically to make ThinLinc. So why is that not the "normal" way if you, the primary project maintainers, are doing things that way when generating your product? On 10/31/13 5:13 AM, Pierre Ossman wrote: > Because that patch is not needed when you build things the "normal" way. > vncviewer will depend on libfltk.so, which will resolve it's own need of > libpng.so. The problem appears because you're trying to link FLTK > statically. This is not a method that is particularly well supported > with today's development tools. > > The major issue is how do you follow dependency chains to figure out > what to pull in? Unfortunately the answer is by hand. Which makes it > impossible to write a generic build system as the dependencies will > depend on what versions of libraries you have, how they are compiled, > your platform, your compiler, etc. > > Still, this is something that has been bothering me. So although I > think we should recommend linking dynamically as the "official" way, we > could see if we can make it easier to hack together a static build. > Perhaps provide examples for certain configurations. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Tigervnc-users mailing list Tigervnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-users
