> But I don't think you are allowed to distribute binaries of your
QT-Windows
> lyx. QT(Windows) is not GPL compatible.
Very true!
However, Trolltech suggests that the GPL license has the option for an
expection on the linkage to non-system libraries with a different license.
This exception has
> >
> > TODO:
> > -make a proper win32 fork controller
>
> The forked controller is only really used by the graphics code at the
moment.
> In turn, conversion to a loadable format is controlled through a
> LyX-generated shell script. Presumably this will also have to be replaced
by
> some sort of
Hi,
just to show you all that I'm quite content with the Qt2 frontend nearing
completion, here's a screenshot of 1.3.0 cvs on win32:
http://www.xs4all.nl/~ps28/ruurd/lyx_win32.png
It has been built using qt 2.3.0 non-commercial for windows, M$ Visual
Studio, the intel 6.0 compiler and stlport.
> > Yes. I had to compile an older version of gs to get around this.
gs-6.51.
> No problem here with gs-7.05 and fname.eps.gz
> Garst
>
Claus, have you already tried to use the native win32 ghostscript?
Epstopdf is included in MikTex, so you could use that with the proper path
conversions. Or, y
> > Yes. I had to compile an older version of gs to get around this.
gs-6.51.
> No problem here with gs-7.05 and fname.eps.gz
> Garst
>
Claus, have you already tried to use the native win32 ghostscript?
Epstopdf is included in MikTex, so you could use that with the proper path
conversions. Or, y
> > Yes. I had to compile an older version of gs to get around this.
gs-6.51.
> No problem here with gs-7.05 and fname.eps.gz
> Garst
>
Claus, have you already tried to use the native win32 ghostscript?
Epstopdf is included in MikTex, so you could use that with the proper path
conversions. Or, y
> > Yes. I had to compile an older version of gs to get around this.
gs-6.51.
> No problem here with gs-7.05 and fname.eps.gz
> Garst
>
Claus, have you already tried to use the native win32 ghostscript?
Epstopdf is included in MikTex, so you could use that with the proper path
conversions. Or, y
When updating a pdf file using pdflatex, changes in the intermediate .tex
file are not detected. It turns out that the .tex file doesn't end up in the
.dep file.
It's easy to see why the .tex file is not being detected by the log file
regex filter in LaTeX.C by looking at the log file:
This is
+EXTRA_DIST = lyxstring.C lyxstring.h regex.c lyxregex.h os_unix.C
shouldn't os_os2.C, os_win32.C and os.h be in here too?
--Ruurd
>OK, while applying the patch, I saw that there are no change logs!
>Ruurd, could you provide some asap? We need to document all the
here they are.
>changes that are done in the patch. There are other problems here and
>there under unix (you did not test that, did you?), but I am in the
>process
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]
>Sent: maandag 14 mei 2001 14:43
>To: [EMAIL PROTECTED]
>Cc: LyX Developers; Claus Hentschel; [EMAIL PROTECTED]
>Subject: Re: [PATCH] os class for OS/2 & Win32 support final version
>
Here's the final (?) version of my win32 patch. Details are in the
README.Win32. I've also attatched a patch for the 116 branch.
--Ruurd
os_spec2_116.diff.bz2
os_spec2_120.diff.bz2
>Subject: Re: [PATCH] os class for OS/2 & Win32 support
>
>
>Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
>
>> It seems to me that at the time SMiyata submitted it more for comments
>> than actual inclusion. Anyway, I think we really need something like
>> that.
>
>Yes, but one of the reason w
after reading the raging debate over Win32 ports I decided to take a look at
the patches Claus Hentschel and I made. To my surprise I found out that
Miyata Shigeru had already wrapped up my patch in a nice os:: class
(Thanks!!!). Is there a reason that it hasn't been submitted to CVS as
yet???
I'
>All this should be moved to some support file, that only gets
>included/built when we are compiling on a __CYGWIN__ environment.
>
>I guess we could add a src/os/ directory similar to src/frontends to
>take care of things like this.
>
>from int main(...) we can then just call something like:
>
>o
At this momemt, lyx compiles almost out of the box on win32 using the cygwin
environement, except for one little detail:
--- lyxserver.C Wed Oct 11 20:47:48 2000
+++ lyx-devel/src/lyxserver.C Wed Oct 11 13:51:18 2000
@@ -72,7 +72,7 @@
// provide an empty mkfifo() if we do not have one. This di
16 matches
Mail list logo
