Results 1 to 4 of 4

Thread: 4.2 and lupdate

  1. #1
    Join Date
    Mar 2006
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post
    Qt products
    Qt3 Qt4
    Platforms
    Windows

    Default 4.2 and lupdate

    I've updated from 4.1.4 to 4.2.0 and have found that running lupdate no longer generates any output for me. I get no error messages and the .ts files remain untouched. If I run the lupdate from v4.1.4 using the same project file, my translation files do get updated though.
    I have tried deleting the existing .ts files, but I still get no output.

    Anyone else having similar issues with lupdate?

  2. #2
    Join Date
    Jan 2006
    Location
    Germany
    Posts
    52
    Thanks
    1
    Thanked 1 Time in 1 Post
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows

    Default Re: 4.2 and lupdate

    Yes, I saw the same thing. No clue what happend. The app must still work however because when I use it integrated in the QDevelop IDE it does work and extracts all the string resources out of the projects source files. I have to find out how QDevelop does invoke the command...

  3. #3
    Join Date
    Jan 2006
    Posts
    156
    Thanked 12 Times in 12 Posts
    Qt products
    Qt3 Qt4
    Platforms
    Unix/X11 Windows

    Default Re: 4.2 and lupdate

    In QDevelop, the command is :
    Qt Code:
    1. lupdate projectName.pro
    To copy to clipboard, switch view to plain text mode 
    QDevelop, an complete Integrated Development Environment for Qt 4: http://qdevelop.org

  4. #4
    Join Date
    Mar 2006
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post
    Qt products
    Qt3 Qt4
    Platforms
    Windows

    Default Re: 4.2 and lupdate

    OK, finally got tired of having to run the 4.1.4 version and decided to look into this. It appears that between 4.1.4 and 4.2.0, lupdate started checking the extension of the passed project file. For projects, it expects a .pro extension. Unfortunately, the export function (added by Trolltech's qt-vsaddin-collection) exports the project as a .pri file, so no output is generated. So, changing the extension to .pro should allow lupdate to function properly once again.

    Sorry jlbrd, if that is what you were implying, I totally missed the message.

Similar Threads

  1. Replies: 5
    Last Post: 22nd September 2006, 08:04

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.