On 8/22/11 7:36 AM, Pierre Ossman wrote: > AFAICT libtool used -fPIC by default for the convenience stuff (i.e. > noinst_*). I initially intended to add a knob for it, but I changed my > mind as PIC is basically harmless on x86_64 (AFAIK). In other words, > since the stuff I committed should do the right thing<tm> in every case > anyway, why would we need a setting for it?
What I was envisioning was more a convenience mode whereby you could use the CMake build system to trigger a vnc.so build, but I need to know how vnc.so is normally built first so I can look at scripting it. I was also trying to validate the patch Martin submitted to build vnc.so out of tree. Minimally, I would like to see what you did put into a macro, or figure out some way that the same 4-line comment doesn't get duplicated half a dozen times in the build system. I also don't understand the comment "It should be on archs as well". I think you may be missing an adjective. ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
