On Thu, Jul 02, 2009 at 12:00:01AM -0400, Ben M. wrote: > On Wed, Jul 1, 2009 at 5:32 PM, Enrico Forestieri<for...@lyx.org> wrote: > > Then, gcc3 is the current default in cygwin and gcc4 must be explicitly > > installed and selected as default through the alternatives mechanism, > > or used through appropriate configure variables. > > Oh, I figured it was the default since that's what we use on the Wiki. > In that case, I agree that we don't need a patch it.
Until I was stuck on Qt 4.2.3 (only with version 4.5.0 Qt became usable on non-Windows, non-Linux systems) I was using gcc3 because the 4.2.3 sources needed to be further patched to allow compilation with gcc4. After discovering where the problem was lying, I was able to compile 4.2.3 with gcc4 and noticed a boost in performance, so I switched to gcc4 even if it was not the default compiler. Compiling Qt 4.5 with gcc4 produces a library that, performance wise, is comparable to Qt4.2/gcc3. Still, when opening the file dialog, a delay of 2-3 seconds before it gets populated seems unavoidable (compare that with instantaneous population when using Qt4.2). This is not a cygwin problem, because I see the same behaviour on Solaris, for example, and it is much more acceptable than the almost 20 seconds delay I was getting with Qt 4.3 and 4.4. > On Wed, Jul 1, 2009 at 5:52 PM, Enrico Forestieri<for...@lyx.org> wrote: > > Is there any objections in setting the svn:executable property on > > the ttf fonts? > > > > The problem is that on Windows, for reasons that are beyond me, the > > ttf fonts are not seen if they don't have the executable bit set. > > I decided to explore this myself, wondering if I should file a Cygwin > bug report. However, as I'm sure Enrico knows, it's a bizarre Windows > quirk. Remove execute permissions from a .ttf file, and Windows > simply refuses to recognize it as a font. This is a Windows quirk, indeed, not a Cygwin one. > > A more ambitious goal would be adding a cygwin-package target such > > that "make cygwin-package" in development/cygwin builds a lyx package > > ready to be installed through the cygwin installation tool ;-) > > Yes! ;-) > > Give me the necessary time (don't hold your breath, though :) and I'll > > see what I can come up with. It will help if you can provide the > > generic-build-script above. I see you used the official cygwin directives > > for building a package. I never found the time to go through all the > > official instructions and I build a cygwin package and accompanying > > setup.ini file by (mostly) hand ;-) > > I halfway obeyed the official instructions. I posted my personal > packaging script earlier, but made some subsequent corrections. > Attached is the newer version, now filled with comments explaining > what I'm doing. Hopefully it'll save you lots of time! Thanks, it sure will. > To generate an official cygwin package, we might want two targets: > cygwin-binpackage and cygwin-srcpackage. I have a real life and duties, and already don't get enough sleep, but I'll see what I can do. No promises, though. -- Enrico
