Joost Verburg <[EMAIL PROTECTED]> writes:
> Thanks for these detailed instructions. Maybe it would be a good idea to
> update the old build_lyxwin script to automate parts of the process. If
> this is not going to happen, make sure that it's removed so it won't
> confuse people.
I'll try and do
Michael Gerz wrote:
> I cleaned up and updated my compile instructions (see attachment). If
> you like to, you can have a look at my file and update INSTALL.Win32
> accordingly (sorry, I will have no time before next weekend).
Thanks for these detailed instructions. Maybe it would be a good idea
[EMAIL PROTECTED] wrote:
I think INSTALL.Win32 is seriously out of date and needs to be looked over
by someonw who knows this stuff... Here's a patch where I'm *guessing* -
it should *not* be applied as it is.
I changed 'MinSYS' be changed into 'MSYS', is that correct?
Does the procedure descr
Jean-Marc Lasgouttes wrote:
"So, what is the situation wrt windows?
Who is planning to provide binaries? How?"
-
Michael Gerz wrote:
"I can have a look at Angus' scripts and see if
they still work (with the exception of automake)."
Joost Verburg <[EMAIL PROTECTED]> writes:
> It is indeed true that MinGW is extremely slow and building takes
> several hours. However, since some Visual C++ functions differ slightly
> from the MinGW functions I had problems like console windows popping up
> after building with Visual C++. Did
Angus Leeming wrote:
Maybe I'm confused.
I think that I did build LyX 1.4 once or twice once I'd managed to turn off the
g++ safe iterators but the link time was over one hour with dynamic linking and
about 50 minutes with static linking.
I then went on to use Asger's VS2003 solution file and b
Michael Gerz <[EMAIL PROTECTED]> writes:
>
> Angus Leeming wrote:
>
> >I don't think that the 1.4 stuff has ever worked, because I never ever could
> >build LyX 1.4 with mingw/msys.
> >
> >
> Really? Why did we have all the dynamic vs. static Qt lib discussion if
> you never managed to build
Am Montag, 27. Februar 2006 18:49 schrieb Michael Gerz:
> Let's assume that Lars or JM have run automake before LyX 1.4.0 is
shipped.
We don't need to assume that, it is a must, part of the corresponding
makefile rule and has happened so far for every release.
Georg
Angus Leeming wrote:
I don't think that the 1.4 stuff has ever worked, because I never ever could
build LyX 1.4 with mingw/msys.
Really? Why did we have all the dynamic vs. static Qt lib discussion if
you never managed to build 1.4.0?
Michael
Paul wrote:
http://gnuwin32.sourceforge.net/packages/automake.htm
I tested this version some time ago but I ran into a problem (I don't
remember the details).
Let's assume that Lars or JM have run automake before LyX 1.4.0 is shipped.
Michael
Abdelrazak Younes wrote:
Paul a écrit :
I've never used automake before (I don't do much in the way of
programming) but
I noticed that version 1.9.4 is available here:
http://gnuwin32.sourceforge.net/packages/automake.htm
I tried this version of automake as well. No success. Probably a pa
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > The autotools are perl scripts, yes. However, if you're feeding a
> > native Windows tool a file path like /foo/bar then it's quite likely
> > to interpret that as switches, no?
> I don't know. I see that there is no 'aclocal.m4' in my SVN reposito
Angus Leeming a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
http://gnuwin32.sourceforge.net/packages/automake.htm
Hum, this is a perl script not an executable. I installed it in the
mingw directory and tried (under msys) to launch 'autogen.sh' from trunk
svn. It stops with:
Using a
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > http://gnuwin32.sourceforge.net/packages/automake.htm
>
> Hum, this is a perl script not an executable. I installed it in the
> mingw directory and tried (under msys) to launch 'autogen.sh' from trunk
> svn. It stops with:
>
> Using automake (GN
Paul a écrit :
I've never used automake before (I don't do much in the way of programming) but
I noticed that version 1.9.4 is available here:
http://gnuwin32.sourceforge.net/packages/automake.htm
Hum, this is a perl script not an executable. I installed it in the
mingw directory and tried (u
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> Angus, do you have any plans to work on the Win32 build scripts?
>> IIRC the 1.3.7 and 1.4.0 files are not in sync.
Angus> I don't think that the 1.4 stuff has ever worked, because I
Angus> never ever could build LyX 1.4 with mingw/msy
I've never used automake before (I don't do much in the way of programming) but
I noticed that version 1.9.4 is available here:
http://gnuwin32.sourceforge.net/packages/automake.htm
The website says:
The GnuWin32 project provides Win32-versions of GNU tools, or tools with a
similar open source l
Michael Gerz <[EMAIL PROTECTED]> writes:
>
> Joost Verburg wrote:
>
> > INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin.
> >
> > However, the Windows build scripts also do not work in the current
> > state. The reason is that automake 1.9 is not yet available for
> > Win
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Enrico Forestieri a écrit :
> > Abdelrazak Younes ...> writes:
> >
> >> For Msys/mingw binaries, I might be able to help if needed. Packaging is
> >> something else... Uwe might propose something and Angus might come out
> >> of his retirement
Michael Gerz a écrit :
Abdelrazak Younes wrote:
Building of svn version with current MSYS DTK is not possible because
of old automake. But I guess that automake is not required for
building a released candidate.
Reading the user list, I see that some people managed to use Cygwin
for that task
Enrico Forestieri a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
For Msys/mingw binaries, I might be able to help if needed. Packaging is
something else... Uwe might propose something and Angus might come out
of his retirement . I can see some well positioned outsiders (Enrico?
Micha
Jean-Marc Lasgouttes wrote:
So, what is the situation wrt windows? Who is planning to provide
binaries? How?
Up to now, I used my self-made recipe to generate LyX binaries (see
former discussion on "static" vs. "dynamic" qt library).
I can have a look at Angus' scripts and see if they stil
Joost Verburg wrote:
INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin.
However, the Windows build scripts also do not work in the current
state. The reason is that automake 1.9 is not yet available for
Windows. Currently I can only get it to compile using automake in a
Abdelrazak Younes wrote:
Building of svn version with current MSYS DTK is not possible because
of old automake. But I guess that automake is not required for
building a released candidate.
Reading the user list, I see that some people managed to use Cygwin
for that task too (using Qtwin port w
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote:
>> However, the Windows build scripts also do not work in the current
>> state. The reason is that automake 1.9 is not yet available for
>> Windows.
Andre> Why do we ne
On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote:
> However, the Windows build scripts also do not work in the current
> state. The reason is that automake 1.9 is not yet available for Windows.
Why do we need automake 1.9 at all?
I.e. waht crucial feature of 1.9 do we and need to u
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> For Msys/mingw binaries, I might be able to help if needed. Packaging is
> something else... Uwe might propose something and Angus might come out
> of his retirement . I can see some well positioned outsiders (Enrico?
> Michael?).
It is my intent
Jean-Marc Lasgouttes a écrit :
"Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> However, the Windows build scripts also do not work in the
Joost> current state. The reason is that automake 1.9 is not yet
Joost> available for Windows. Currently I can only get it to compile
Joost> usin
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> However, the Windows build scripts also do not work in the
Joost> current state. The reason is that automake 1.9 is not yet
Joost> available for Windows. Currently I can only get it to compile
Joost> using automake in a Cygwin envir
> "christian" == christian ridderstrom <[EMAIL PROTECTED]> writes:
christian> Hi, I think INSTALL.Win32 is seriously out of date and
christian> needs to be looked over by someonw who knows this stuff...
christian> Here's a patch where I'm *guessing* - it should *not* be
christian> applied as i
[EMAIL PROTECTED] wrote:
Hi,
I think INSTALL.Win32 is seriously out of date and needs to be looked over
by someonw who knows this stuff... Here's a patch where I'm *guessing* -
it should *not* be applied as it is.
INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin.
However
Hi,
I think INSTALL.Win32 is seriously out of date and needs to be looked over
by someonw who knows this stuff... Here's a patch where I'm *guessing* -
it should *not* be applied as it is.
I changed 'MinSYS' be changed into 'MSYS', is that correct?
Does the procedure described in this file even
32 matches
Mail list logo
