OS2World OLD-STATIC-BACKUP Forum

WebSite Information => Article Discussions => Topic started by: miturbide on 2011.09.18, 06:48:58

Title: Qt version 4.7.3
Post by: miturbide on 2011.09.18, 06:48:58
http://www.os2world.com/content/view/21096/2/ (http://www.os2world.com/content/view/21096/2/)

I tried to install QT 4.7.3 with RPM.

- Removed the old QT with WarpIn
- Installed rpm-yum-bootstrap-1_3.wpi and the FHS structure was created in C:\.
- run on the command prompt "yum install libqt4". The instructions says it is not necessary, but I wanted to try how to install the libraries with RPM. I don't know if there is already an QT4 app on the rpm server to test how will install automatically QT4.

It seems to download fine the packaged but it get an error when installing it.
(http://www.os2world.com/component/option,com_smf/Itemid,63/action,dlattach/topic,3809.0/attach,1453/image/)

I was unable to find warpin-conflicts.exe file on the hard drive.

Any idea what is the reason for this error? was is something wrong uninstalling the old QT? or is some other procedure missing with RPM?
Title: Re: Qt version 4.7.3
Post by: diver on 2011.09.18, 12:22:09
It Seems your rpm is too old . after installing the bootstrap do a Yum update. this should update rpm And also installing the missing exe
Title: Re: Qt version 4.7.3
Post by: miturbide on 2011.09.18, 15:09:00
Hi

I had run "yum update".
It had downloaded something and process ok.

But after that I run "yum install libqt4" and I get the same error.
Title: Re: Qt version 4.7.3
Post by: diver on 2011.09.18, 15:41:16
Try "yum install rpm" it help for others
Title: Re: Qt version 4.7.3
Post by: miturbide on 2011.09.18, 15:49:08
it worked that way. Thanks.
Title: Re: Qt version 4.7.3
Post by: Barbara on 2011.09.18, 16:35:41
Needs also coreutils, failure.
Any suggestion?
Thanks.
Title: Re: Qt version 4.7.3
Post by: ivan on 2011.09.18, 23:23:05
Using the zip version, or should I sat trying to use the zip version, on our test machine.  Followed the instructions in the install.os2 file - directory of choice = e:\os2\apps\qt4.

Tried to run some of the 18 test applications we use, some give a little disk activity and that's it.

some give an error message as follows:
09-18-2011  16:45:05  SYS2070  PID 00f6  TID 0001  Slot 00b1
G:\QT4-APPS\SIGIL\SIGIL.EXE
QSVGIE4->QTCORE4.__ZN9QListData11detach_growEPii
127

The only difference between the applications is the second line - the name of the application.

To test that there wasn't something wrong with the applications I deleted the e:\os2\apps\qt4 directory and copied over the 4.6.3 version from backup - all applications work as they should.

Now what???

ivan
Title: Re: Qt version 4.7.3
Post by: Tellie on 2011.09.18, 23:49:36
hihi,

Thats when you have a version mismatch, due you had a older dll somewhere in path.
If you have qt 4.7.3, then you have to be sure there is no 4.6.3 dll in path or whatever, cause then you get that error.
Title: Re: Qt version 4.7.3
Post by: ivan on 2011.09.19, 01:39:20
Thanks Tellie, found qthelp4.dll in os2\dll - why it was there is a good question that I will try and find the answer to tomorrow because we used warpin to install 4.6.3 and I used warpin to uninstall it.

ivan
Title: Re: Qt version 4.7.3
Post by: CDRWSel on 2011.09.23, 17:02:29
Hello,

Where is the QT 4.7.3 WPI package ?  (one click to install)
RPM/YUM not working, not wanted not enough space on my SSD disk etc...
I already have previous QT installed through WPI and WPI is needed to maintain WPI db.   
 
ZIP package will not update current installed WPI packages and is not good in this case.

:-\
Title: Re: Qt version 4.7.3
Post by: StefanZ on 2011.09.23, 19:16:07
I would also appreciate WPI version....
Title: Re: Qt version 4.7.3
Post by: DougB on 2011.09.23, 19:48:04
I think they are not planning to supply a WPI version. There is a ZIP version, and the instructions are pretty simple (I haven't tried installing it yet). Basically, it says: completely uninstall what you have, unzip to some place on a drive, then add a couple of paths to your CONFIG.SYS. The whole directory structure has changed, again, so you would need to uninstall what you already have before installing the new one anyway.

It does mean that you need to manage it yourself, but that seems to be the goal of the RPM/YUM project. A second goal seems to be to fill up your hard disk (preferably on the boot drive) with useless junk. Somebody must own shares in a disk company.

In fact, it should be quite easy to build a WPI installer, but I haven't tried that either. It should be easier than trying to figure out RPM/YUM, especially if you already have some *NIX type programs installed, since they will have to be changed to work with the RPM/YUM stuff. When I tried RPM/YUM, SAMBA quit working because UNIXROOT got changed.
Title: Re: Qt version 4.7.3
Post by: Pete on 2011.09.23, 20:12:56
Hi All

With regards to the qt473 zip file: Am I the only person who thinks that the root directory for this software should be simply qt4 rather than qt4-4.7.3-1?

With the root directory as qt4 there would be no need to change the config.sys Path and Libpath to install a new version and no need to reboot afterwards to activate those changes: simply delete existing qt4 directory and then unzip the new build in the same location and you are ready to go.

I did create a Ticket about this in the qt4 bugtracker a couple of days ago but it looks like the ticket has been removed as I cannot find it listed in the current ticket list.

Maybe it is all a plot to make us use yum/rpm...


Regards

Pete
Title: Re: Qt version 4.7.3
Post by: DougB on 2011.09.23, 22:04:03
Many packages add the version number to the base folder name. Personally, i always remove that so that it is easier to replace it when the time comes.

Complaining about the way that a developer packages their work, is likely a waste of time. After all, as noted in the RPM/YUM thread, "the developer knows best" (yeah, right). Just fix it, and get on with life.

QuoteWith the root directory as qt4 there would be no need to change the config.sys Path and Libpath to install a new version and no need to reboot afterwards to activate those changes: simply delete existing qt4 directory and then unzip the new build in the same location and you are ready to go.

Unfortunately, that is probably not the case. A package like QT4 contains a lot of DLLs, some of which get loaded at boot time, and they stay there until the system is shut down. If you don't reboot, you will likely end up with a mix of old and new, until you do reboot. That could cause problems, and will probably end up forcing you to do a non planned reboot. It also appears that the new package has a different directory structure (again), so it may still require modifications to CONFIG.SYS, and a reboot, to make it work. That is just plain old fashioned poor programming, but it is what we get.
Title: Re: Qt version 4.7.3
Post by: Pete on 2011.09.23, 22:41:02
Hi Doug

No, qt4 dlls do not get loaded at boot - unless you have something in your startup folder that needs them.

If all the fgiles supplied in a later qt4 package are within the root directory for that package it does not matter if the directory structure within the package changes - unless some or all of the dll files get moved from the bin subdirectory.

Regards

Pete
Title: Re: Qt version 4.7.3
Post by: DougB on 2011.09.23, 23:14:49
Two things:

Yes, I load QLIPSHARE at boot time.

I had missed the part where the older WPI packages load themselves into the eCS directory, so BIN was sort of hidden from view (another good reason to not do stupid things like that).

I uninstalled the old QT4, using WarpIn, and that seems to have worked fine. I then unzipped the new file into C:\QT4 and added the C:\QT4\BIN directory to both LIBPATH, and PATH. Rebooted, and reinstalled QLIPSHARE to make it work. Everything else (that I use) seems to be working.
Title: Re: Qt version 4.7.3
Post by: melf on 2011.09.24, 00:11:26
I forgot that I installed the older qt4 with warpin, so I just deleted the content of my old qt4-folder and put the new one's there and added the new path. This didn't work and I realised there were conflicting dlls, so I deleted all dlls beginning with qt4 i C:\ecs\dll and that worked fine. It is a simple install really and I can't see the need of RPM - which has been said to be needed due to complicated dependences and so on. Well, Warpin had worked great.
Title: Re: Qt version 4.7.3
Post by: rudi on 2011.09.24, 09:23:09
Quote from: Pete on 2011.09.23, 20:12:56
I did create a Ticket about this in the qt4 bugtracker a couple of days ago but it looks like the ticket has been removed as I cannot find it listed in the current ticket list.

Maybe it is all a plot to make us use yum/rpm...

No it isn't. The there is a reply to your ticket and it has been closed. If you look at http://svn.netlabs.org/qt4/timeline (http://svn.netlabs.org/qt4/timeline) you will find it right on the  top.
Title: Re: Qt version 4.7.3
Post by: CDRWSel on 2011.09.24, 12:39:10
Quote from: DougB on 2011.09.23, 23:14:49
Two things:

Yes, I load QLIPSHARE at boot time.

I had missed the part where the older WPI packages load themselves into the eCS directory, so BIN was sort of hidden from view (another good reason to not do stupid things like that).

I uninstalled the old QT4, using WarpIn, and that seems to have worked fine. I then unzipped the new file into C:\QT4 and added the C:\QT4\BIN directory to both LIBPATH, and PATH. Rebooted, and reinstalled QLIPSHARE to make it work. Everything else (that I use) seems to be working.

Ok, i'll give a try of the zip file according all suggestion I could read.
If it is easy to update, i'll check previous WPI path structure and try to build a WPI model for QT. The nice with WPI is that it can run some extra user code...
Title: Re: Qt version 4.7.3
Post by: Pete on 2011.09.24, 16:09:21
Hi rudi

Yes, I see the ticket using http://svn.netlabs.org/qt4/timeline

However, my point was that the ticket is not visible using View Tickets which is where I expected to find it.

Regards

Pete


Title: Re: Qt version 4.7.3
Post by: Pete on 2011.09.24, 16:10:36
Hi doug

So, you'd need to close QLIPSHARE before updating qt4.

Regards

Pete
Title: Re: Qt version 4.7.3
Post by: DougB on 2011.09.24, 19:27:02
Quotei'll check previous WPI path structure and try to build a WPI model for QT.

Actually, it is just as easy to simply unzip the new one, then put the paths in CONFIG.SYS You still have to uninstall the old one (using WarpIn) before doing that. Why they want to complicate a very simple install, by using RPM/YUM, I will never understand. Even using WarpIn is more complicated.

QuoteSo, you'd need to close QLIPSHARE before updating qt4.

Yes, but it isn't difficult to do the update anyway. I simply forgot about that program, since it just sits there, and works. It is very convenient when I need to copy something from one system to another.

In fact, I moved the QT4 directory to my programs/data disk, and now I have ONE copy of the QT4 directory that is used by both of my boot systems. That saves about 40 meg on each of my boot disks. I am going to move the EMX stuff too, but that makes less difference (about 760K).
Title: Re: Qt version 4.7.3
Post by: StefanZ on 2011.09.24, 20:28:46
xsystray.dll is not part of the compiled release?  :-[
Title: Re: Qt version 4.7.3
Post by: Paul Smedley on 2011.09.25, 09:01:35
Quote from: DougB on 2011.09.24, 19:27:02
That saves about 40 meg on each of my boot disks.

In the days or terabyte hard drives, people are really still concerned about 40mb of files?
Title: Re: Qt version 4.7.3
Post by: CDRWSel on 2011.09.25, 11:39:25
Terabyte disk are only good to put user datas or archived files.
Now, mostly older PCs are using mecanical hard drive as boot partition 

Today, boot OS is installed on high speed disk. Most nice systems uses SSD (16GB, 32GB or 40GB)
This is the way where it goes (very quick boot time and application respns time. So do new tablette etc... SSD build in)
     
SSD above 40GB are too expansive and not interesting !
As soon more OSes are installed or a backup boot partition is created, the real available space could drop to less than 10GB and when you know that to peserve SSD lifetime, you need a lot of free space to allow the buildin firmware to correctly optimize nand utilization, the size could drop less than 5GB for a correct usage !

Yes, big programs could be a problem and reduce SSD lifetime (this was't te case of mecanical HD)
Programmers should take care of this evolution to be up to date.
Cheers
Title: Re: Qt version 4.7.3
Post by: DougB on 2011.09.25, 19:50:25
QuoteIn the days or terabyte hard drives, people are really still concerned about 40mb of files?

Yes. Not because of a lack of disk space, but because it takes time to back up 40 MB of files. If I can put that onto a common disk, that gets backed up every night, I don't have to back it up when i back up the boot disks. Personally, I take as much stuff off of the boot disks as possible (well, not quite), so that I don't have to reinstall a bunch of stuff when I do an OS update. I find that I can share a lot of it between different boot systems too. Like QT4, on a drive that I use with both eCS 2.0, and eCS 2.1, makes it easier to keep the "older" system up to date, because I just have to update it once, and both systems benefit.

QuoteTerabyte disk are only good to put user datas or archived files.

This is not entirely true. You CAN put boot drives on Terabyte disks. You just need to follow the directions found on the eCS 2.1 install CD (and fight with windows to use the disk geometry installed by eCS, if you want to install windows too).

I really question the desirability of using SSD on a desktop system. They can be useful on a laptop (or the like) because they are more likely to be "shocked", but performance (for more expense) is a trade off for long life. Performance is also affected by using a file system with a large cache (JFS). Of course, every user has different requirements (please take note, for those who seem to think that RPM/YUM is desirable), and every system can be tweaked to perform as the user wants. If SSD really buys you something, then use one, but I suspect that most people will find little actual difference, until they drop their portable device.
Title: Re: Qt version 4.7.3
Post by: ivan on 2011.10.12, 17:15:29
I think I've found another problem with this version of Qt4.

We use SIR 2.1.1 for image resizing - at least we did until the upgrade of Qt4.  The output from the cameras is JPG which SIR handled very well in the past - now that format doesn't even appear in the conversion dropdown.

To check the problem I restored the older version of Qt4 from backup to one workstation and the JPG option appeared and I could resize the JPGs as before.

Now I must seriously think about downgrading all the workstations to allow us to continue working, that is unless there is a way for this latest Qt4 to be made to work with standard JPEG graphics files.

Does anyone know of a work round to do this?

ivan
Title: Re: Qt version 4.7.3
Post by: Pete on 2011.10.12, 19:20:52
Hi ivan

I've not used sir before so thought I'd have a look at it.

I see no problem with jpg/jpeg files, they can be added to the action window.

I added a bmp file to the action window and the Target Format dropdown does show jpg and jpeg.

However, sir cannot open the bmp file chosen so cannot convert it to jpg.

I think I'll carry on using PMView or nconvert for my graphics conversions/resizes.

Regards

Pete




Title: Re: Qt version 4.7.3
Post by: Tellie on 2011.10.12, 20:51:11
Hi Ivan,

You mean Sir 2.1.1 from Netlabs
I ported that.
I tried today with qt 4.7.3 and here i can still convert a jpg to png or any other format.

Can you describe what you tried and not worked ?

Mayby i can recompile to 4.7.3

Please email me @ elbert dot pol @ gmail dot com

A picture allways help to show what you mean..
Title: Re: Qt version 4.7.3
Post by: rudi on 2011.10.12, 21:01:47
This is most likely an installation issue. It looks like Qt is not finding it's plugins (in this case the image format plugin for JPEG). How was this Qt installed ? What does the directory structure look like ? Are there any stray "qt.conf" files ?  If everything else fails, it might also help to delete the file %HOME%/.config/trolltech.ini
Title: Re: Qt version 4.7.3
Post by: ivan on 2011.10.12, 23:38:50
Thanks everyone.

The fact Pete said he could see JPG listed started me looking at the differences between the old and new Qt4.

The old didn't have the path in Path and Libpath but had it listed in qtsys.conf in MPTN\etc.
The new has the path listed in Path and Libpath and there was nothing but two dots for the path in the qt.conf in the qt4 dir.

As an experiment I removed one of the dots in path line of qt.conf and now SIR 2.1.1 has started to work again.

I don't know enough about how linux likes the conf files or even what should be in them - I suppose I'll have to try and find out ;)

Thanks for the offer Tellie but I do have one question.  Do you think it would be possible for someone whose last programming was in assembler some 30 odd years ago to port the latest version of Sigil -0.4.3 to OS/2 and if so what would I need?

As I said rudi it was an extra dot in the path statement in the conf file for the new Qt4 version, a conf file I took as being correct but it wasn't for our situation.

So again thanks to all - I can have some sleep tonight and not have any grumbles from anyone in the morning about 'having to do things the hard way'.
Title: Re: Qt version 4.7.3
Post by: rudi on 2011.10.13, 10:11:23
Quote from: ivan on 2011.10.12, 23:38:50
The old didn't have the path in Path and Libpath but had it listed in qtsys.conf in MPTN\etc.

%ETC%/qtsys.conf is no longer used. It was an OS/2 specific invention that - AFAIK - is valid only in 4.6.x version. Here is, how it works now:

The file qt.conf is searched in the specified order in following locations:

1.) in the (Qt-) resource data of the executable
2.) in the current directory
3.) in the directory where QtCore4.dll was loaded from

Then the "prefix" value from qt.conf is appended to the directory where qt.conf was found. This becomes the base directory for all the other stuff like "plugins", "translations", "imports", etc. Note that the names for these subdirs can be overridden - even with absolute paths - in qt.conf as well.

In case no qt.conf could be found, the directory where QtCore4.dll was loaded from will become the base and the subdirs will be assumed to use their default names.

The standard setup uses a directory structure like this:

%QTDIR%/bin
%QTDIR%/plugins
%QTDIR%/plugins/imageformats
...
%QTDIR%/translations

The Qt DLLs reside in %QTDIR%/bin. Thus qt.conf located in the same directory and found by rule 3.) must contain ".." as prefix value.


Quote from: ivan on 2011.10.12, 23:38:50
As I said rudi it was an extra dot in the path statement in the conf file for the new Qt4 version, a conf file I took as being correct but it wasn't for our situation.

So I assume you have changed the directory structure without knowing the implications. This is exactly the type of problems that this new RPM/YUM/FHS stuff is supposed to avoid. Not sure if it does...

Title: Re: Qt version 4.7.3
Post by: ivan on 2011.10.13, 13:12:18
Hi rudi,

Thanks for that explanation, it should be in the readme.

Our setup puts the Qt4 dir in OS/2\apps and we have the qt.conf in OS/2\apps\qt4.  The directory structure is as you list.

If I am understanding correctly what you have written then, in fact, there is no real reason to have the Qt4 dir listed in Path and Libpath at all.

No comment on the RPM/YUM, we had that in another thread.

ivan