Wow, I wasn't expecting for this thread to get so busy all of the sudden.
Thanks ogilin10 for the explanation on Flash not working with Opera; I checked out your pets and recognize those missing libs, as Firefox contains them in its own separate folder.

Gnuxo and greengeek. I haven't tested QT 4.8 and Qupzilla, but if the jpegs show properly in Exprimo, then it is just an incompatability issue between the Exprimo libs and Wary libs. (libjpeg would be my first guess).

If jpegs don't show up in Exprimo, then the problem would most likely be that the Qupzilla pet is buggy.

The Qupzilla pet is not buggy. I'm in Exprimo and the jpegs look good.
If anything, it's probably a library issue. But I don't really pay attention to those minut details so I'm fine with how Qupzilla works in Solidpup.

Should I just accept that I should not use Qupzilla on SPTINT2? or is there a chance that I could substitute a library from Exprimo?

I have attached an image of the libjpeg files and symlinks I find in /usr/lib. Does that give any useful info?

If I wanted to add a lib that would potentially make Qupzilla work here, is it likely I would need to recompile something? (I don't really have a need to get Qupzilla working as Opera is working really well for me now - it's just that there is obviously something I could learn from this and I like tinkering...)

@Gnuxo - would you have time to post a similar screenshot from Exprimo?

It is not recommended to mix libs from from different based derivatives, as it can corrupt your system. But it might not be a big deal for you, if you know to to reverse the problem.

My understanding is that Exprimo uses Debian Squeeze libs, and Wary 5.1.1 uses libs based on an older version of Ubuntu (I don't know exactly which one, but it is older than Lucid).

The proper method would be to compile the latest QT in Solidpup and then compile Qupzilla. Yes, it is a lot of work, so I understand why someone would rather use a pet from a different based distro. If anyone is up to the challenge and wants to compile apps for Solidpup, I will add them to the Solidpup repo. If nobody answers the challenge, I may take a crack at compiling QT and Qupzilla myself, when the motivation arises.

Right now, I am working on something unrelated to Puppy, except that I am using Openshot in Puppy to do it.

Thanks Tman. I think it is about time I learned what this compiling thing is all about so I will do some research and start tinkering under the hood a bit.

No problem. Compiling takes time and patience to learn. You should start off by compiling small, simple apps. With the more complicated apps, you need to download and compile the dependencies first and then compile the app.
Also some sources need hacking before they can compile properly. A lot of times, some Googling will lead you to the answers, but real hacking requires that you understand how to program in the language that the source code was written in.

I've attached a script that I've made to build shed hex editor automatically.
I don't know if shed will be of any use to you, but by examing the script, you can figure out the steps I used for it. Just remove the fake .gz extension to rename it back to build_shed-1.15.sh

To run the script:
1) load the devx file for Solidpup with sfs-load
2) cd to the folder where you downloaded the script
3) from the terminal, type: sh build_shed-1.15.sh

By running the script, you can see in the terminal what goes on during the compile process.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum