Get the new PortableApps.com Platform 10.0: Gorgeous themes, a full portable app store and advanced functionality
Announcing the World's Best Flash Drive: The PortableApps.com Companion | Did you see a malware warning on Friday?
|
Qt Creator Portable 1.2.0 Development Test 2
dagardner - July 10, 2009 - 1:36pm
Application: Qt Creator
Category: Development
Description: Qt Creator is a new cross-platform integrated development environment (IDE) tailored to the needs of Qt developers. Qt Creator is available bundled together with the latest Qt libraries and additional development tools as part of the Qt SDK, which provides everything you need to get started with cross-platform Qt development in a single install.
Qt Creator Portable 1.2.0 Development Test 2 [165.34 MB download / 1.07 GB installed]
(MD5: 7b12597bedc6685f22831e2c93626de0)
Release Notes:
Development Test 2 (2009-08-05):
- Fixed issue for finding portable Qt
- Save the registry settings (HKCU\Software\Nokia)
- Did some clean up in the registry (needs checking with other Qt programs)
Development Test 1 (2009-07-10): Initial Release
Notes:
- It's big; really big. I need to look into reducing the size.
- Tried to compress the whole thing but that caused it to crash. I need to see what files can be compressed without causing a crash.
- Includes a fair amount of source code, but not the source code for Qt Creator *shrug*. Need to figure out what is actually needed and package the rest as an optional install.
|
Dang it!
I guess this isn't ready for testing yet. There appears to be an environment variable or something that I am missing that prevents Qt Creator from finding the installation of Qt. When I did my install, there must have been a version of Qt in the path because when I moved to a VM it didn't work.
Back to the drawing board.
looks like we might need a
looks like we might need a commonfiles QT
Once again, unlikely
The Qt runtime is the only bit which could be made common with any benefit whatsoever, but there's the standard problem with different versions - mainly Qt 3 and 4 (though 3 has the troublesome "[Non-Commercial]" appendix on all windows which has blocked it so far here. I think Qt 4 would be the only one needing consideration. Nevertheless, there's also the problem with different Qt modules. All up, I don't think it's worth the trouble (anything in Common Files is troublesome for end users, parallel directories and all that). And it won't help at all for Qt Creator.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I don't think that's the problem
Qt Creator has everything it needs under one directory. The standard Qt Creator installer puts everything it needs under a single directory. Qt Creator has an INI file that tells it where the compiler and the Qt files are, but for some reason, Qt Creator Portable can't find those files. I am going to step through the source to see how it Qt Creator locates these.
It also looks like Qt Creator has the ability to build off of different versions of Qt, but I haven't looked into how to do that yet. I will likely included in the installer code that will determine when Qt Creator Portable is being upgraded to a new version of Qt to keep the older versions, if desired.
My experience is that Qt programs don't need a commonfiles directory Windows Qt programs need a dll, but that is it and is usually included with the distributed Qt program.
Now it works!
Or at least it worked on my VM. Please try it out and let me know what needs fixing. I'm going to look into including other versions of Qt.
Thinking of looking at this again...
I thought I would look at this again, and I happened come across a discussion thread about making Qt Creator portable for Windows.
It appears that Qt Creator looks for plug-ins and the SDK is a fixed location that is determined at install time.
One person said that they installed Qt Creator on a TrueCrypt drive so they could take it with them, but they also suggested using the
substcommand.What would be the implications of using the
substcommand for a PortableApp?Has anyone done that with another app?(yes, people have. Should have searched first.) Would that be considered a acceptable solution?I'll look more into this to see whether it is a viable option.
Well
I doubt that it would be considered acceptable for a PortableApp to require a SUBST drive (especially considering that the SUBST drive may not be open on all systems [e.g. Say you choose P: well on one of my systems P: is the card reader in my printer, or Z: I may have a network share mapped there, etc.])
It would be better to use the system built into PAL 2.0 (or PAL 2.1) for Registry and File editing (using %PAL:Drive% and %PAL:LastDrive% to make changes).
~3D1T0R
Better, true...
I agree that it is better, but the last time I tried to look at it, I was never able to find all of the places where the drive letter needed to be changed. The good news is that that was before the new Launcher scripting infrastructure so it may be possible now.
DevTest:
I'd recommend that you do your best portablizing it with the File and Registry editing systems available, then put out a new DevTest, and make a note when you post it that you'd appreciate any help finding any other places where it references an absolute path.
Then the community here can help you out.
~3D1T0R