Thanks. I worked it around by installing qt5 devtools and qmake and hardcoding its path. Easy but works like charm.
-- Marcin 2014-07-17 11:52 GMT+02:00 Andrey Kozhevnikov <coderusin...@gmail.com>: > you can login [1] to Mer VM and do what you want manually > > [1] https://sailfishos.org/develop-faq.html > > 17.07.2014 15:38, Marcin M. пишет: > > And how can I run the mer's lupdate & lrelease from terminal? > > -- > Marcin > > > 2014-07-17 11:36 GMT+02:00 Marcin M. <marmistrz...@gmail.com>: > >> Thanks >> >> 1. The problem is that Tools/External/lupdate doesn't do anything. I >> created translations/harbour-myapp-pl.ts, ran Tools/External/lupdate and >> the pl translation file didn't change. >> >> My .pro looks like that: >> >> TARGET = harbour-myapp >> >> CONFIG += sailfishapp >> >> SOURCES += src/harbour-myapp.cpp \ >> src/settings.cpp >> >> OTHER_FILES += qml/harbour-myapp.qml \ >> qml/cover/CoverPage.qml \ >> rpm/harbour-myapp.changes.in \ >> rpm/harbour-myapp.spec \ >> rpm/harbour-myapp.yaml \ >> harbour-myapp.desktop \ >> qml/pages/SettingsPage.qml \ >> qml/pages/MainPage.qml \ >> qml/pages/FontPickerDialog.qml \ >> qml/pages/WelcomeDialog.qml \ >> harbour-myapp.png \ >> translations/harbour-myapp-de.ts \ >> translations/harbour-myapp-pl.ts >> CONFIG += sailfishapp_i18n >> TRANSLATIONS += translations/harbour-myapp-de.ts \ >> translations/harbour-myapp-pl.ts >> >> HEADERS += \ >> src/settings.h >> >> What's missing here? >> >> -- >> Marcin >> >> >> 2014-07-17 10:51 GMT+02:00 Luca Donaggio <donag...@gmail.com>: >> >> 1. No, lupdate is included in the virtual machine used to bild your >>> app and invoked automatically >>> 2. Just put your harbour-yourappname-xx.ts files into 'translations' >>> directory and you're set >>> 3. Usually I install the RPM in the emulator and run it from command >>> line after changing LANG env variable >>> >>> >>> On Thu, Jul 17, 2014 at 10:37 AM, Marcin M. <marmistrz...@gmail.com> >>> wrote: >>> >>>> I couldn't find the answers to a couple of questions: >>>> 1. Does SailfishOS SDK require external lupdate? If yes, where can the >>>> command for lupdate be set (as of Mint 17 (Ubuntu 14.04), lupdate-qt5 is >>>> not provided by any package) >>>> 2. If using sailfishapp_i18n, are the QTranslator steps still needed? >>>> Should /usr/share/appname/i18n or .../appname/translations be used? If ` - >>>> '%{_datadir}/%{name}' ` is already in .yaml is anything else needed >>>> concerning packaging? >>>> 3. What's the recommended way of testing translations in the Emulator? >>>> setting LANG in the environmental variables? >>>> >>>> PS. There's no documentation concerning this on the sailfishos.org >>>> website. >>>> -- >>>> Marcin >>>> >>>> _______________________________________________ >>>> SailfishOS.org Devel mailing list >>>> To unsubscribe, please send a mail to >>>> devel-unsubscr...@lists.sailfishos.org >>>> >>> >>> >>> >>> -- >>> Luca Donaggio >>> >>> _______________________________________________ >>> SailfishOS.org Devel mailing list >>> To unsubscribe, please send a mail to >>> devel-unsubscr...@lists.sailfishos.org >>> >> >> > > > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org > > > > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org >
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
