"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "README" between
fet-5.47.0.tar.bz2 and fet-5.47.1.tar.bz2

About: FET allows to automatically schedule a timetable for e.g. of a school, high-school or university.

README  (fet-5.47.0.tar.bz2):README  (fet-5.47.1.tar.bz2)
This is FET version 5.47.0 This is FET version 5.47.1
Program description: Program description:
FET is free timetabling software (licensed under the GNU Affero General P ublic License version 3 or later). FET is free timetabling software (licensed under the GNU Affero General P ublic License version 3 or later).
This program aims to automatically generate the timetable of a school, hi gh-school or university. This program aims to automatically generate the timetable of a school, hi gh-school or university.
It may be used for other timetabling purposes. It may be used for other timetabling purposes.
FET can mean "Free Educational Timetabling" (the "E" in the middle may al so stand for other words, based on your personal preference). FET can mean "Free Educational Timetabling" (the "E" in the middle may al so stand for other words, based on your personal preference).
FET homepage: https://lalescu.ro/liviu/fet/ FET homepage: https://lalescu.ro/liviu/fet/
Requirements: Requirements:
FET is created in the following environment: openSUSE Tumbleweed GNU/Linu FET is created in the following environment: openSUSE Tumbleweed GNU/Linu
x distribution, Linux 5.8.7, Xfce 4.14, x distribution, Linux 5.9.8, Xfce 4.14,
Xfce Terminal Emulator 0.8.9.2, Midnight Commander 4.8.25, Krusader 2.7.2 Xfce Terminal Emulator 0.8.9.2, Midnight Commander 4.8.25, Krusader 2.7.2
, Kate 20.08.1, KDiff3 0.9.98, grep 3.4, sed 4.8, , Kate 20.08.3, KDiff3 0.9.98, grep 3.5, sed 4.8,
Thunar Bulk Rename 1.8.15, Qt 5.15.1, Qt Creator 4.13.0, gcc 10.2.1, g++ Thunar Bulk Rename 1.8.16, Qt 5.15.2, Qt Creator 4.13.3, gcc 10.2.1, g++
10.2.1, make 4.3, gdb 9.2, Valgrind 3.16.1, 10.2.1, make 4.3, gdb 9.2, Valgrind 3.16.1,
Coverity Scan 2019.03, Cppcheck 2.1, SpeedCrunch 0.12, Inkscape 1.0.1, GI Coverity Scan 2019.03, Cppcheck 2.2, SpeedCrunch 0.12, Inkscape 1.0.1, GI
MP 2.10.20, ImageMagick 7.0.10, tar 1.32, gzip 1.10, MP 2.10.22, ImageMagick 7.0.10, tar 1.32, gzip 1.10,
bzip2 1.0.8, other great software (most of them are free software, in the sense defined by The Free Software Foundation). bzip2 1.0.8, other great software (most of them are free software, in the sense defined by The Free Software Foundation).
The executable version of FET for Windows is obtained in the following en vironment: Windows 10 operating system, The executable version of FET for Windows is obtained in the following en vironment: Windows 10 operating system,
Command Prompt, Total Commander 9.51, Notepad, Python 2.7.18, Qt 5.15.1, Qt Creator 4.13.0, MinGW 8.1.0, 7-Zip 19.00. Command Prompt, Total Commander 9.51, Notepad, Python 2.7.18, Qt 5.15.2, Qt Creator 4.13.3, MinGW 8.1.0, 7-Zip 19.00.
FET is a C++ application and uses Qt, a C++ toolkit for cross-platform ap plication development. FET is a C++ application and uses Qt, a C++ toolkit for cross-platform ap plication development.
FET can be run on any platform supported by Qt (GNU/Linux, Windows, Mac O S X, and maybe others). FET can be run on any platform supported by Qt (GNU/Linux, Windows, Mac O S X, and maybe others).
You will need a C++11 compliant C++ compiler to compile FET. You will need a C++11 compliant C++ compiler to compile FET.
GNU/Linux, Mac OS X: GNU/Linux, Mac OS X:
For running, you need only the archive of FET compiled for your operating system (which contains the necessary libraries). For running, you need only the archive of FET compiled for your operating system (which contains the necessary libraries).
For compiling, you will need this software: For compiling, you will need this software:
make 4.2.1 or similar (GNU Make). make 4.2.1 or similar (GNU Make).
gcc 10.2.1 or similar. gcc 10.2.1 or similar.
g++ 10.2.1 or similar (or gcc-g++, or gcc-c++, the name may vary. This program may be included in the gcc package). g++ 10.2.1 or similar (or gcc-g++, or gcc-c++, the name may vary. This program may be included in the gcc package).
Qt 5.15.1 or compatible (The authors also tried to maintain backw Qt 5.15.2 or compatible (The authors also tried to maintain backw
ards source compatibility with Qt 4.v.v). ards source compatibility with Qt 4.v.v,
but it seems that on some systems such an old Qt might no
t work correctly).
Note: You need a C++11 compliant C++ compiler. You might be able to use the Clang C++ compiler or other C++ compiler instead of gcc and g++. Note: You need a C++11 compliant C++ compiler. You might be able to use the Clang C++ compiler or other C++ compiler instead of gcc and g++.
Windows: Windows:
For running, you need only the archive of FET compiled for Windows (which contains the necessary dll-s). For running, you need only the archive of FET compiled for Windows (which contains the necessary dll-s).
For compiling, you need Qt and a compatible C++ compiler complying with t he C++11 standard (MinGW is a possibility). For compiling, you need Qt and a compatible C++ compiler complying with t he C++11 standard (MinGW is a possibility).
Download: Download:
You can download the latest version from the FET homepage, https://lalesc u.ro/liviu/fet/ You can download the latest version from the FET homepage, https://lalesc u.ro/liviu/fet/
skipping to change at line 67 skipping to change at line 68
(Once installed, I think you'll need to open the Xcode app to finish the installation.) (Once installed, I think you'll need to open the Xcode app to finish the installation.)
Windows: you need a Qt compatible C++ compiler. Windows: you need a Qt compatible C++ compiler.
Maybe an easy option is the MinGW compiler, available optionally with the Qt distribution or on the Qt download page. Maybe an easy option is the MinGW compiler, available optionally with the Qt distribution or on the Qt download page.
(You might also download MinGW from the internet. There might be more var iants. One of them is on: http://mingw-w64.org/) (You might also download MinGW from the internet. There might be more var iants. One of them is on: http://mingw-w64.org/)
Getting - compiling - installing Qt: Getting - compiling - installing Qt:
Qt homepage: https://www.qt.io/ Qt homepage: https://www.qt.io/
You will need Qt 5.15.1 or compatible to compile FET (The authors also tr You will need Qt 5.15.2 or compatible to compile FET (The authors also tr
ied to maintain backwards source compatibility with Qt 4.v.v). ied to maintain backwards source compatibility with Qt 4.v.v,
but it seems that on some systems such an old Qt might not work c
orrectly).
You can get the corresponding version of Qt with your package manager or from the internet (preferably from the Qt homepage). You can get the corresponding version of Qt with your package manager or from the internet (preferably from the Qt homepage).
Qt can be used with the GNU (L)GPL or commercial license (The authors cho se the GNU (L)GPL license). Qt can be used with the GNU (L)GPL or commercial license (The authors cho se the GNU (L)GPL license).
GNU/Linux: It is possible to use YaST (or Adept Manager) or other package managers to get your version of Qt, pre-compiled. GNU/Linux: It is possible to use YaST (or Adept Manager) or other package managers to get your version of Qt, pre-compiled.
Or you can download, (possibly) compile and install Qt from the internet (preferably from its homepage). Or you can download, (possibly) compile and install Qt from the internet (preferably from its homepage).
A possible name for the precompiled package is libqt5. A possible name for the precompiled package is libqt5.
A user reported that on Ubuntu "sudo apt-get install qt5-default" without quotes should work. A user reported that on Ubuntu "sudo apt-get install qt5-default" without quotes should work.
Windows - Download latest Qt from the internet (preferably from its homep age). There are available precompiled packages, but the authors chose Windows - Download latest Qt from the internet (preferably from its homep age). There are available precompiled packages, but the authors chose
to compile Qt from the sources using the additional configure option "-sc hannel". This is done to ensure that SSL will work in FET using the to compile Qt from the sources using the additional configure option "-sc hannel". This is done to ensure that SSL will work in FET using the
skipping to change at line 91 skipping to change at line 93
(When we tried to use the recommended option "-opengl dynamic" we got a c ompiler error.) (When we tried to use the recommended option "-opengl dynamic" we got a c ompiler error.)
Note that to be able to open ui files with Qt Designer or ts files with Q t Linguist you need to install the Qt component qttools Note that to be able to open ui files with Qt Designer or ts files with Q t Linguist you need to install the Qt component qttools
(or the whole Qt package). (or the whole Qt package).
Mac OS X: Mac OS X:
Maybe you can get pre-compiled Qt packages for Mac OS X. If not, get Qt f rom the internet (preferably from its homepage). Maybe you can get pre-compiled Qt packages for Mac OS X. If not, get Qt f rom the internet (preferably from its homepage).
Note about the Qt "QMAKESPEC" variable: advanced topic, read this if you get Qt errors about the environment not being set, or environment Note about the Qt "QMAKESPEC" variable: advanced topic, read this if you get Qt errors about the environment not being set, or environment
variable QMAKESPEC not being set, or if the Qt environment is not set cor rectly: Qt needs to know the environment you are using. It is usually variable QMAKESPEC not being set, or if the Qt environment is not set cor rectly: Qt needs to know the environment you are using. It is usually
something like: linux-g++, macx-g++ or win32-g++ (platform-compiler). You can find all the supported platforms in the directory "mkspecs" of Qt something like: linux-g++, macx-g++ or win32-g++ (platform-compiler). You can find all the supported platforms in the directory "mkspecs" of Qt
(some usual locations are /usr/share/qt5/mkspecs or /usr/lib/qt5/mkspecs on GNU/Linux or C:\Qt\5.15.1\mkspecs on Windows). (some usual locations are /usr/share/qt5/mkspecs or /usr/lib/qt5/mkspecs on GNU/Linux or C:\Qt\5.15.2\mkspecs on Windows).
It seems that Qt automatically finds the platform (there is a default con figuration in the "default" subdirectory of the "mkspecs" directory, It seems that Qt automatically finds the platform (there is a default con figuration in the "default" subdirectory of the "mkspecs" directory,
which is created automatically when you install Qt). If the default confi guration is not working or is wrong, you may need to set the which is created automatically when you install Qt). If the default confi guration is not working or is wrong, you may need to set the
correct QMAKESPEC variable for your platform. Under Windows, you can crea te an environment variable QMAKESPEC equal to win32-g++ correct QMAKESPEC variable for your platform. Under Windows, you can crea te an environment variable QMAKESPEC equal to win32-g++
(if you are using MinGW), under other platforms create an environment var iable named QMAKESPEC equal with the correct platform-compiler (if you are using MinGW), under other platforms create an environment var iable named QMAKESPEC equal with the correct platform-compiler
you are working on (for instance macx-g++ or linux-g++). you are working on (for instance macx-g++ or linux-g++).
Compiling FET: Compiling FET:
You will need a C++11 compliant C++ compiler to compile FET. You will need a C++11 compliant C++ compiler to compile FET.
skipping to change at line 145 skipping to change at line 147
and and
"linux-g++*: QMAKE_CFLAGS_RELEASE -= -g" "linux-g++*: QMAKE_CFLAGS_RELEASE -= -g"
(without quotes) in the files src/src.pro and src/src-cl.pro (you can ad d them at the end of these files, or in another proper location). (without quotes) in the files src/src.pro and src/src-cl.pro (you can ad d them at the end of these files, or in another proper location).
Note NMkJobs: advice from a user: if you have a multiple core computer, y ou may be able to split the compilation into more threads, with the -j option fo r the Note NMkJobs: advice from a user: if you have a multiple core computer, y ou may be able to split the compilation into more threads, with the -j option fo r the
make command, so that the compilation is faster. This option creates a nu mber of compilation threads equal with the number specified along with the -j op tion. make command, so that the compilation is faster. This option creates a nu mber of compilation threads equal with the number specified along with the -j op tion.
Under GNU/Linux or Mac OS X, just write "make -j 2" if you have dual core or "make -j 4" if you have quad core (in case you have quad core and you want Under GNU/Linux or Mac OS X, just write "make -j 2" if you have dual core or "make -j 4" if you have quad core (in case you have quad core and you want
to keep a core free for other tasks, write "make -j 3"). This is proven t o work under GNU/Linux and Mac OS X. Under Windows it depends on the C++ compile r (you to keep a core free for other tasks, write "make -j 3"). This is proven t o work under GNU/Linux and Mac OS X. Under Windows it depends on the C++ compile r (you
may try it to see if it works). may try it to see if it works).
Currently FET can be compiled with a C++ compiler, using Qt version 5.15. 1 or compatible. Currently FET can be compiled with a C++ compiler, using Qt version 5.15. 2 or compatible.
Note NUseSystemLocale: If you want FET to autodetect the system locale la nguage, type <<qmake fet.pro "DEFINES+=USE_SYSTEM_LOCALE">> Note NUseSystemLocale: If you want FET to autodetect the system locale la nguage, type <<qmake fet.pro "DEFINES+=USE_SYSTEM_LOCALE">>
or simply <<qmake "DEFINES+=USE_SYSTEM_LOCALE">>. This will work if you r ecompile from the beginning all the FET package (remove or simply <<qmake "DEFINES+=USE_SYSTEM_LOCALE">>. This will work if you r ecompile from the beginning all the FET package (remove
all the intermediary files and recompile), and also if you did not use FE T on this machine or if you remove the settings file/registry entry for FET all the intermediary files and recompile), and also if you did not use FE T on this machine or if you remove the settings file/registry entry for FET
(otherwise FET will retain the language which was already saved in its se ttings). (otherwise FET will retain the language which was already saved in its se ttings).
Note4: If you get an error like this: Note4: If you get an error like this:
In file included from ../../Qt5.3.2/5.3/gcc_64/include/QtGui/qopenglconte xt.h:62:0, In file included from ../../Qt5.3.2/5.3/gcc_64/include/QtGui/qopenglconte xt.h:62:0,
from ../../Qt5.3.2/5.3/gcc_64/include/QtGui/QtGui:32, from ../../Qt5.3.2/5.3/gcc_64/include/QtGui/QtGui:32,
from ../../Qt5.3.2/5.3/gcc_64/include/QtWidgets/QtWidgetsDepends: 3, from ../../Qt5.3.2/5.3/gcc_64/include/QtWidgets/QtWidgetsDepends: 3,
skipping to change at line 169 skipping to change at line 171
# include <GL/gl.h> # include <GL/gl.h>
^ ^
compilation terminated. compilation terminated.
you may need to install additional packages before compiling FET. For ins tance, under openSUSE GNU/Linux you may need to install Mesa-devel. you may need to install additional packages before compiling FET. For ins tance, under openSUSE GNU/Linux you may need to install Mesa-devel.
As reported by a user, on Mint GNU/Linux he needed to install mesa-common -dev and libgl1-mesa-dev. As reported by a user, on Mint GNU/Linux he needed to install mesa-common -dev and libgl1-mesa-dev.
Note 5: If you only want to compile the command-line version, open the fi le fet.pro with a text editor and from the second line remove the Note 5: If you only want to compile the command-line version, open the fi le fet.pro with a text editor and from the second line remove the
text "src/src.pro ". text "src/src.pro ".
GNU/Linux: GNU/Linux:
- You will need Qt 5.15.1 or compatible to compile this program. - You will need Qt 5.15.2 or compatible to compile this program.
- type "qmake fet.pro" or simply "qmake". You have to use qmake from Qt 5 series, which on some systems - type "qmake fet.pro" or simply "qmake". You have to use qmake from Qt 5 series, which on some systems
might be named qmake-qt5 (this command is executed very fast, so don't wo rry if you get immediate return from it) might be named qmake-qt5 (this command is executed very fast, so don't wo rry if you get immediate return from it)
See also notes NUseSystemLocale and Note4 above. See also notes NUseSystemLocale and Note4 above.
- type "make" (this takes a long time, maybe even 1 hour). See also note NMkJobs above. - type "make" (this takes a long time, maybe even 1 hour). See also note NMkJobs above.
To remove the compiled objects/executable: "make clean" and/or "make dist clean". To remove the compiled objects/executable: "make clean" and/or "make dist clean".
Mac OS X: Mac OS X:
3 Variants: 3 Variants:
1. First variant, if you use the gcc compiler: 1. First variant, if you use the gcc compiler:
- You will need Qt 5.15.1 or compatible to compile this program. - You will need Qt 5.15.2 or compatible to compile this program.
- type "qmake fet.pro" or simply "qmake". You have to use qmake from Qt 5 series. - type "qmake fet.pro" or simply "qmake". You have to use qmake from Qt 5 series.
(this command is executed very fast, so don't worry if you get immediate return from it) (this command is executed very fast, so don't worry if you get immediate return from it)
- IMPORTANT: you might need to write: "qmake -spec macx-g++ fet.pro", if "qmake fet.pro" - IMPORTANT: you might need to write: "qmake -spec macx-g++ fet.pro", if "qmake fet.pro"
does not produce a correct makefile. does not produce a correct makefile.
See also notes NUseSystemLocale and Note4 above. See also notes NUseSystemLocale and Note4 above.
- type "make" (this takes a long time, maybe even 1 hour). See also note NMkJobs above. - type "make" (this takes a long time, maybe even 1 hour). See also note NMkJobs above.
To remove the compiled objects/executable: "make clean" and/or "make dist clean". To remove the compiled objects/executable: "make clean" and/or "make dist clean".
2. Another variant: 2. Another variant:
- Type "qmake fet.pro" and then "xcodebuild". - Type "qmake fet.pro" and then "xcodebuild".
3. Another variant, if you use the Clang C++ compiler (which seems to be the default for Qt 5.15.1 on Mac): 3. Another variant, if you use the Clang C++ compiler (which seems to be the default for Qt 5.15.2 on Mac):
It seems that you need to type: It seems that you need to type:
"/Users/Yourname/Qt5.15.1/5.15.1/clang_64/bin/qmake -r -spec /Users/Yourn ame/Qt5.15.1/5.15.1/clang_64/mkspecs/macx-clang", then "make" "/Users/Yourname/Qt5.15.2/5.15.2/clang_64/bin/qmake -r -spec /Users/Yourn ame/Qt5.15.2/5.15.2/clang_64/mkspecs/macx-clang", then "make"
(the -r parameter might not be necessary.) (the -r parameter might not be necessary.)
Please see: https://lalescu.ro/liviu/fet/forum/index.php?topic=2488.msg13 425#msg13425 (and also see the whole topic there.) Please see: https://lalescu.ro/liviu/fet/forum/index.php?topic=2488.msg13 425#msg13425 (and also see the whole topic there.)
Windows: MinGW C++ compiler: you need Qt 5.15.1 or compatible, and MinGW. Windows: MinGW C++ compiler: you need Qt 5.15.2 or compatible, and MinGW.
You might use other C++ compilers if you want, please see the Qt document ation. You might use other C++ compilers if you want, please see the Qt document ation.
for other variants. Any C++ compiler that supports Qt should be good. for other variants. Any C++ compiler that supports Qt should be good.
You need to run "qmake fet.pro" or "qmake" (this command is executed very fast, so don't worry if you get You need to run "qmake fet.pro" or "qmake" (this command is executed very fast, so don't worry if you get
immediate return from it) and then, if you are using MinGW, "mingw32-make " (this takes a long time, maybe even 1 hour) immediate return from it) and then, if you are using MinGW, "mingw32-make " (this takes a long time, maybe even 1 hour)
in a command line in the FET directory. in a command line in the FET directory.
See also note NUseSystemLocale above. See also note NUseSystemLocale above.
See also Note4 above. See also Note4 above.
See also note NMkJobs above. See also note NMkJobs above.
(You can use the command line prompt of Windows or the Qt command line pr ompt shortcut in the Qt shortcuts menu.) (You can use the command line prompt of Windows or the Qt command line pr ompt shortcut in the Qt shortcuts menu.)
Then, you can remove the directories "src" and "tmp", to save up space, i f you want. Then, you can remove the directories "src" and "tmp", to save up space, i f you want.
 End of changes. 12 change blocks. 
21 lines changed or deleted 25 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)