| Summary: | ksquirrel doesn't load codecs thus is unable to open any image | ||
|---|---|---|---|
| Product: | TDE | Reporter: | pitriss <chytrex> |
| Component: | non-core programs | Assignee: | Slávek Banko <slavek.banko> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Debian Wheezy | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2246 | ||
| Attachments: |
Fix quotes in pkgconfig file
Fix missing Qt=>TQt renaming in ui files Fix run codecs configurator Fix FTBFS with clang |
||
|
Description
pitriss
2015-07-11 15:35:02 CDT
The bug is in the pkg-config file for libksquirrel. I also found that it lacking Qt => TQt renaming in .so.ui files (libksquirrel). And thirdly, there is a problem with running Codec manager using tdesu. Patches for all the problems I have prepared. I'll push them soon... Created attachment 2529 [details]
Fix quotes in pkgconfig file
Created attachment 2530 [details]
Fix missing Qt=>TQt renaming in ui files
Created attachment 2531 [details]
Fix run codecs configurator
Created attachment 2532 [details]
Fix FTBFS with clang
Ouch, I'll still have to work on a problem, because the current solution causes FTBFS on Ubuntu 10.04 (Lucid). I tested that using CFLAGS with quotation marks in pkg-config file is very problematic - escaping of quotation marks does not work reliably. One soulution causes ksquirrel FTBFS in Lucid, second solution causes FTBFS in Squeeze. It seems that more reliable way is define parameters without additional escaped quotes and let ksquirrel to use stringify for these parameters. I'll do the patches in this way. It seems that Ksquirrel is only user of libksquirrel. So it will not require changes in other modules. It should be finally fixed! If you are using the Preliminary stable builds, you can update and verify it. (In reply to Slávek Banko from comment #8) > It should be finally fixed! If you are using the Preliminary stable builds, > you can update and verify it. Sorry I'm using stable build :( (In reply to pitriss from comment #9) > (In reply to Slávek Banko from comment #8) > > It should be finally fixed! If you are using the Preliminary stable builds, > > you can update and verify it. > > Sorry I'm using stable build :( Ok, in that case we will believe that I fixed it :) |