Small task for Windows programmers

[wysota]

No, I'm looking for a volunteer I'm not experienced in Windows. I don't know how to add an entry to the menu from within a script, etc.

Are you volunteering?

Do you think this is a sane idea at all? It's just something that came to my mind after compiling Qt on Windows...

[marcel]

. I don't know how to add an entry to the menu from within a script, etc.

You can go around that and copy the links to the start menu folder.

But I'll see what I can do when I have the time, maybe in the weekend. That is if someone doesn't do it till then.

[wysota]

But I don't have the links. I don't have a binary release installed, just the source. So the steps needed are:
1. create links
2. create a folder in the start menu
3. move links to the above mentioned folder
4. create a script that will setup all the vars
5. create a link that will run the script
6. move the link (or the script directly) to the folder
7. say "voilla"

[marcel]

But I don't have the links. I don't have a binary release installed, just the source. So the steps needed are:
1. create links
2. create a folder in the start menu
3. move links to the above mentioned folder
4. create a script that will setup all the vars
5. create a link that will run the script
6. move the link (or the script directly) to the folder
7. say "voilla"

Voilla!
Since what you asked for is not possible with a batch script, I turned my head towards WSH. So you guys can find enclosed a small vb script, which you can test. If your Windows installation is somehow missing wscript, then you're out of luck, but normally, it should be there.
The script will prompt you to enter the Qt instalation root, such as C:\Qt\4.3.2 and it will do the work from there.

Currently it creates shortcuts for all the 4 tools and command prompt, and also creates a qtvars.bat which sets the environment. The makespec is hardcoded to win32-g++.

To run the script, just double-click it.

[wysota]

Great! I'll test it tomorrow. Unfortunately I'll be testing it with msvc, but I understand fixing the specs shouldn't be much work.

[marcel]

Great! I'll test it tomorrow.

It works fine for me, on Vista even, with UAC enabled. But some users have very strict security configurations (I call it paranoia) so the scripting host might be disabled.

So, if possible, someone should test it on XP too, but my opinion is that if it works on Vista with UAC it should work very well on XP.

If not, the only alternative is a native application that does the very same thing. Something like an installer.

Unfortunately I'll be testing it with msvc, but I understand fixing the specs shouldn't be much work.

Yes, just modify the line txtStream.WriteLine("set QMAKESPEC=win32-g++") with what you need, and also the comment above it. Or, edit the generated batch file.

BTW, Qt should be already compiled when you run the script . If not, it will probably throw some runtime errors. I didn't exactly handled them all.

[wysota]

I wonder if it's possible to auto detect the specs like Qt does. The script could then be extended to find it itself.

[marcel]

What do you mean? Qt knows because it's reading the QMAKESPEC env variable.

[wysota]

What do you mean? Qt knows because it's reading the QMAKESPEC env variable.

I mean to be able to auto detect the specs from within the script to set the variable in the first place. If QMAKESPEC is not set, I know qmake tries (and often manages) to detect it. Maybe the script could use it somehow... but it would require qmake to dump the information somewhere, maybe it does...

[jpn]

Perhaps "qmake -query" and/or $QTDIR\.qmake.cache could help somehow? Basically it should be enough to ask for the location of qmake.exe and everything else could be then figured out..

[wysota]

Under Linux in the specs directory there is a soft link called "default" that points to the default specs. I don't know if there is anything similar on Windows, but that could be a way to detect the specs.

If we can't make it all happen from within a script, maybe a small statically compiled app using QWizard would be an option as well...

[marcel]

Under Linux in the specs directory there is a soft link called "default" that points to the default specs. I don't know if there is anything similar on Windows, but that could be a way to detect the specs.

If we can't make it all happen from within a script, maybe a small statically compiled app using QWizard would be an option as well...

I thought of this too.
I think I'm gonna make a wizard that also let's you fully configure, compile and install Qt Open Source.
I don't know if I'm gonna write it with Qt or when it's gonna be ready, but I hope sometime soon.

[marcel]

Perhaps "qmake -query" and/or $QTDIR\.qmake.cache could help somehow? Basically it should be enough to ask for the location of qmake.exe and everything else could be then figured out..

I don't think we can use that... qmake -query QMAKE_MKSPECS only gives you the path where the make specs are located.

but it would require qmake to dump the information somewhere, maybe it does...

Maybe have the script output a test program and then call qmake and parse its output?
I don't really trust this method. What if qmake can't tell the correct make spec?

What do you think about letting the user choose the make spec/compiler in the script interface?

[Brandybuck]

Are you volunteering?

No! I don't know much about Windows either. Which is why I use NSIS or BitRock to install Qt apps on that godforsaken platform.

[marcel]

No! I don't know much about Windows either. Which is why I use NSIS or BitRock to install Qt apps on that godforsaken platform.

I first want to say that I literally hate Windows and any other MS product! But "godforsaken"? Come on guys... That operating system is more popular among developers than all the other platforms.
I don't know much about the IT industries int you countries, but how does a developer can earn a decent buck there? From Linux programming? A .NET or JEE developer makes far more money than a developer doing c/c++ in Linux . I think that's a fact, at least for the past few years and at least a few to come.

[wysota]

For me it's easier to find a well paid assignment abroad than to look for it in Poland. I would probably find something I'd like to work on, but I doubt I'd be satisfied with the financial side of it. That's why it says "freelancer" in my LinkedIn profile.