Am 20.03.2012 10:04, schrieb Vincent van Ravesteijn:
What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have changed
and Peter did a good
job with the script so that the former manual settings are now automatically
set.
It still worked perfectly for me. What didn't work anymore ?
You cannot compile Qt 4.8 as described. First you will stumble over the problem that a window pops
up telling you that you have to install Perl. This is a known bug of the Qt package. But even if you
put in the workaround fix, you will stumble over compilation errors for which one can again find
workarounds. Finally I found out that the precompiled Qt 4.8.0 comes already with all you need and
now supports MSVC 2010. So in fact handling Qt is now as simple as installing a program with a few
clicks.
Which settings had to be set manually
which are now set automatically ?
The CMAKE variable settings, see the diff of my change for a list of them. (All
;-) )
At some point you say "where you copied the dependencies to". I have no idea
what you mean with this.
This was also not clear in the old version. I now added a further step:
It suddenly requires CMakeScript
This is the official CMake release plus a script that is provided directly by
Peter. So we have
the maintainer in our team.
I'm not sure whether Peter is still in our team.
I think yes.
If you were a CMake expert, ok. But if there is a CMake problem, you come to
the list and ask others
to fix it. Now suddenly you promote tools which are only used by yourself.
Peter suggested it and it works much faster, in my opinio this is an advantage. If you don#t like
the script, you still can either use CMAKE without the script of the version I linked and remove the
ninja option as I described. For security reasons the build script doesn't use it for release
builds. (However I could find an issue.)
The Install.Win32 file is for new developers. I guess existing developers will never read it as they
already have their setup. So I tried to make it as simple as possible.
No other developer have
ever heard of CMakeScript before, let alone about Ninja. You nowhere even
explains what Ninja is ?
It is an alternative to Make. I also don't know the details how it internally sets up filelists and
dependencies and don't want to. But what I see is that compiling LyX using Ninja is much faster and
thus saves a lot of time. Just check it out.
Have you tried it? It generates studio files and solutions for debugging too.
No,
Why are you then telling it does not?
but you don't mention it at all in the file.
I'm using MSVC since the beginning and I would not have accepted it if I could not debug with MSVC.
Why should I explicitly mention the solution files? I can but for just compiling LyX you don't need
them. If you want to debug LyX you will but the Install-Win32 file was not about debugging LyX. But
if you like I can add a section about this.
> I'm afraid that this will generate a merged build by default which is rather
useless to use in
> MSVC.
Please test and then be afraid.
Why do you then have to manually supply the path to the dependencies ? The
previous workflow did
this automatically.
If you don't have then or the path to them is not correct they will be downloaded. But it might be
that you already have them. Then you don't need them twice. For example I started compiling master
and got the dependencies. But when compiling branch they would be downloaded again. But to save disk
space I changed the build script in my branch checkout to the folder of the dependencies that were
downloaded once for master.
Maybe my description is not clear enough or I indeed have a bug in the script, thus please test and
I'll fix it or you can change the description to make things more clear.
In what way do you have to be a CMake expert to use the GUI ? Start the gui,
browse to the correct
folder, and check some options. What is difficult ?
Maybe you remember that I had to ask on the list how this is done. And when switching to branch or
from branch I had to do this again.
CMake searched for Qt, so if it could find it,
there was no need to supply it manually. The GNUWin32 directory was set
automatically.
Not on my setup.
So, you
prefer to do this all manually ?
You only have to set the path once and never again when switching between branches. This is much,
much easier and I don't need to learn the different names of Cmake variables.
Why wouldn't the CMake GUI allow you to compile master and branch parallel ?
I never managed to get this and on this list I was told that this doesn't work and so a script was
proposed.
It doesn't make sense
that you would want to compile both with the same settings.
I do this since 2 years. Why should I use different settings? I only need to distinguish between
release and debug builds, but for this you can call the build script with different parameters as I
described.
Sure, ashes on me. I had some discussions with Peter and getting Qt 4.8 took me
several hours
Why would getting Qt 4.8 takes you several hours ?
Why? Why is your favorite meal your favorite meal? It just happens and I am/was not the only one as
there are hundred complaints about the broken Qt source tarball. I compiled Qt since many years
without problems, now I failed the first time. But as you can see, the Qt handling is now much
easier so no compilation is anymore necessary.
regards Uwe
