OLD - FET-5.23.3 snapshot for testing

Started by Liviu Lalescu, September 19, 2014, 08:38:12 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Liviu Lalescu

Quote from: Zsolt Udvari on September 21, 2014, 09:42:56 AM
Quote from: Liviu Lalescu on September 21, 2014, 07:27:19 AM
Translations need to be in /usr/share/fet/translations/ , always. This is where FET executable searches for them. Maybe you could tell me how to correct this.
Maybe can you set from fet.pro (translations.path)? Maybe this helps.

We need something different. The user to specify the prefix for "make install" and this to be taken as the directory for translations, to be modified in the sources. It is difficult, maybe impossible. So I might be forced to not allow changing the default make install prefix, /usr.

Liviu Lalescu

I have given a thought. Zsolt, I am very sorry, but I gave up on modifying the installation location and other checks. This should be done by a configure script, and I am unable to handle. I guess you need to manually change fet.pro if you want some fine tuning, like disabling GUI or other components.

Alex, I added a manual for fet-cl. Unfortunately, I cannot fix the translations problem, they need to be installed as usual, in /usr/share/fet/translations/ .

I added a new snapshot, please test. The location, as usual, http://lalescu.ro/liviu/fet/download/test/ .

The Windows exe has an icon. If somebody has a Mac, please tell me if that exe also has an icon (the fet executable obtained after compiling and maybe installing).

Zsolt Udvari

Quote from: Liviu Lalescu on September 21, 2014, 01:45:12 PM
I have given a thought. Zsolt, I am very sorry, but I gave up on modifying the installation location and other checks. This should be done by a configure script, and I am unable to handle. I guess you need to manually change fet.pro if you want some fine tuning, like disabling GUI or other components.
Okay, no problem. When I will have time, I'll try it - I think it isn't too difficult.

Liviu Lalescu

I just added a new snapshot, minor improvements.

Liviu Lalescu

I just added a new snapshot, with better icons (higher resolution).

Liviu Lalescu

I have a question for Windows users: please unpack the 7-zip self-extracting archive, do not run fet.exe, just see if this file (fet.exe) has the icon I made (FET and a cube underneath). Maybe see the file in Total Commander, and in Explorer, and create a shortcut on the desktop.

I am using a compressed ico file and it seems that for older programs it is not processed correctly.

In FET it will be always shown correctly. I am referring to the icon representing the file fet.exe.

Tell me your detailed Windows version.

yush

The icons shows up for Mac. See the attached screen shots.

AlexL

If to use
make install INSTALL_ROOT=/path/dir
then translations should be installed into /path/dir/usr/share/fet/translations/
but *.qm are not installed now, dir /path/dir/usr/share/fet/translations was not created.

Liviu Lalescu

#23
Quote from: AlexL on September 22, 2014, 05:55:50 AM
If to use
make install INSTALL_ROOT=/path/dir
then translations should be installed into /path/dir/usr/share/fet/translations/
but *.qm are not installed now, dir /path/dir/usr/share/fet/translations was not created.

The fet.pro file is correct.

It works on my computer, the directory is created and the *.qm files are copied to /path/dir/usr/share/fet/translations/ .

I don't know what to do.

Please tell me, "make install" works correctly on your computer?

AlexL

Quote from: Liviu Lalescu on September 22, 2014, 07:24:16 AM
It works on my computer, the directory is created and the *.qm files are copied to /path/dir/usr/share/fet/translations/ .
I don't know what to do.
Please tell me, "make install" works correctly on your computer?
No, translations *.qm does not install.
You should use more difficult .pro file for installation of translations, for example, https://github.com/viktor-zin/afce/blob/master/afce.pro
qm files is not simple files

Liviu Lalescu

#25
I added a new snapshot, minor improvement.

Alex, the translation files *.qm are available before compiling, so they should be simply copied as in your suggested file above. There is no need for the special ending procedure.

I am sorry, but I think it will remain this way. I cannot find/solve the bug.

AlexL

This string works:
translations.files = translations/*
or string:
translations.files = translations/*.ts
but string:
translations.files = translations/*.qm
does not work
qm files is not simple files

Liviu Lalescu

#27
Please tell me your Qt version and maybe OS (32, 64 bit?)

Please tell me if the attached file works (overwrite, type "make", then "make install"). Tell me if all the files in the fet-5.23.3-snapshot-.../translations/ directory are copied (including the *.qm ones).

But this is not a good solution, because:

1) We should only copy the *.qm files;

2) On my computer (64 bit openSuse 13.1, Qt 5.3.2) it works with *.qm; also on a Mac (reported by Yush), it works.

Liviu Lalescu

I saw this page: https://github.com/leppa/tspsg/blob/master/INSTALL.md

Quote
4.2. General Procedure

On most platforms the general building and installation procedure is:

Run lrelease to generate binary translation files (.qm) from the source (.ts).
Run qmake with CONFIG+=release parameter to generate makefiles.
Run make utility (e.g., make, nmake, mingw32-make) to build TSPSG.
Run make utility with install parameter.
NOTE: It is important to run lrelease before qmake, or qmake will not "pick up" the translations when generating installation rules.

Could you please, using the official snapshot (not the variant in the post above), try if this works? lrelease should be invoked like: go to src/ directory, then type "lrelease src.pro".

But I think this is only a problem for Qt 4; I hope they repaired this problem in Qt 5, at least in the last Qt 5.3.2. Because I would not like to add such a command, because I prefer to keep track of lrelease myself.


AlexL

fet-5.23.3-snapshot-23-sept-2014-08_55.tar.bz2: everything is OK, problem was on my side with translations, I'm sorry.
If you don't want to run fet with current language instead of English, then maybe will you provide patch? I don't see problems with translations. Popular languages are translated more, than 50% and I want to build fet in repo without English only by default. The second way to use option while building. The third way is command line option for fet. Better the second way; if not, then the first way; if not, then the third way.