276 (edited by De-Backer 2020-12-11 11:26:14)

Re: Nouveautés de la version de développement 0.8

De-Backer wrote:
ZASto wrote:

Do not place elements in any Git* repository.
Even KiCAD abandoned Git* plugin as a place for pulling elements from.

your text gives no value without sources
furthermore you do not explain why this is a bad idea.
and to close what is your alternative?

I am always willing to listen to reason, if it is substantiated.

Edit:
I would like to hear the reason for your post, so if possible give us an explanation.

I did some searching on KiCad and:
KiCAD abandoned https://github.com/ will be replaced by https://gitlab.com
see https://github.com/KiCad/kicad-symbols/ … /README.md
https://gitlab.com/kicad/libraries/kica … /README.md

further we would move more towards the same operation of KiCAD
dev =>  qelectrotech-source
librarians => qelectrotech-element
...
or am I mistaken?

Re: Nouveautés de la version de développement 0.8

Update Mxe cross-compile to Qt 5.15.2 for Windows packages, but stay yet on KF5 5.70 version, with KF5 5.76 it didn't found KAutoSaveFile: No such file or directory for  #include <KAutoSaveFile>

https://github.com/KDE/kcoreaddons/commits/master
https://github.com/KDE/kcoreaddons/comm … vefile.cpp

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

Update Mxe cross-compile to Qt 5.15.2 for Windows packages, but stay yet on KF5 5.70 version, with KF5 5.76 it didn't found KAutoSaveFile: No such file or directory for  #include <KAutoSaveFile>

https://github.com/KDE/kcoreaddons/commits/master
https://github.com/KDE/kcoreaddons/comm … vefile.cpp

thanks even on v5.70.0 CMake Generate step failed. Build files cannot be regenerated correctly.

https://invent.kde.org/frameworks/kcoreaddons.git
will be tricky

279 (edited by De-Backer 2020-12-11 19:38:02)

Re: Nouveautés de la version de développement 0.8

@scorpio810
can I push this to the qet git?
see
https://github.com/qelectrotech/qelectr … ker:master

Remove all qm files …
why:
they are created at compile time,
but the existing ones in src dir prevent the ones created in the buid dir
=> no qm files are shipped

otherwise I have to change the dir for the translation in Cmake this is also an option

Re: Nouveautés de la version de développement 0.8

and if I use qmake?

281 (edited by De-Backer 2020-12-12 00:32:47)

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

and if I use qmake?

there are no translations in the build,
i will do a test first, adjust the pro file
and if it works,
then I will forward it.

Cmake start working nomicons/smile

works

# Fichiers de traduction qui seront installes
TRANSLATIONS += $$files(lang/*.ts)

CONFIG+=lrelease

but is in the build dir..

static void printUsage()
{
    printOut(LR::tr(
        "Usage:\n"
        "    lrelease [options] -project project-file\n"
        "    lrelease [options] ts-files [-qm qm-file]\n\n"
        "lrelease is part of Qt's Linguist tool chain. It can be used as a\n"
        "stand-alone tool to convert XML-based translations files in the TS\n"
        "format into the 'compiled' QM format used by QTranslator objects.\n\n"
        "Passing .pro files to lrelease is deprecated.\n"
        "Please use the lrelease-pro tool instead, or use qmake's lrelease.prf\n"
        "feature.\n\n"
        "Options:\n"
        "    -help  Display this information and exit\n"
        "    -idbased\n"
        "           Use IDs instead of source strings for message keying\n"
        "    -compress\n"
        "           Compress the QM files\n"
        "    -nounfinished\n"
        "           Do not include unfinished translations\n"
        "    -removeidentical\n"
        "           If the translated text is the same as\n"
        "           the source text, do not include the message\n"
        "    -markuntranslated <prefix>\n"
        "           If a message has no real translation, use the source text\n"
        "           prefixed with the given string instead\n"
        "    -project <filename>\n"
        "           Name of a file containing the project's description in JSON format.\n"
        "           Such a file may be generated from a .pro file using the lprodump tool.\n"
        "    -silent\n"
        "           Do not explain what is being done\n"
        "    -version\n"
        "           Display the version of lrelease and exit\n"
    ));
}

Re: Nouveautés de la version de développement 0.8

Yeahh enfin! ....
https://img.pixers.pics/pho_wat(s3:700/FO/18/78/35/77/700_FO18783577_61a0ce6f25eac22c2fcc58550ec87e30.jpg,700,264,cms:2018/10/5bd1b6b8d04b8_220x50-watermark.png,over,480,214,jpg)/papiers-peints-smiley-balles-vont-a-une-fete.jpg.jpg

https://download.tuxfamily.org/qet/forum_img_2/fibre.png

jusqu'à 2 Gbit/s partagés de débit descendant (dans la limite de 1 Gbit/s par équipement) et jusqu'à 600 Mbit/s en débit montant entre plusieurs appareils.

Vivement la livebox 6 que je puisse sortir du carton ma 10G Aquantia. ;-)

Çà me change .. plus besoin de passer par mon smartphone en 4G pour uploader les gros paquets QET.

283 (edited by De-Backer 2020-12-13 10:42:12)

Re: Nouveautés de la version de développement 0.8

it would be possible to compile QET with Cmake via QT-SDK without Compiling KDE frameworks.
does anyone want to test this?
note there will still be errors and elements that are missing
I'm still working on that.

edit: add build instructions

git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror.git qet && cd qet
mkdir build && cd build
mkdir l10n
cmake ..
make

run:

./qelectrotech

Re: Nouveautés de la version de développement 0.8

For now I need found a solution for fix new KF5 KCoreAddons:

n file included from ../sources/diagram.h:27:0,
                 from ../sources/conductorautonumerotation.cpp:23:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcontent.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/ui/titleblockpropertieswidget.h:23:0,
                 from ../sources/configpages.h:22,
                 from ../sources/configdialog.cpp:20:
../sources/ui/../qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/conductornumexport.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:21538 : la recette pour la cible « release/conductorautonumerotation.o » a échouée
make[1]: *** [release/conductorautonumerotation.o] Erreur 1
make[1]: *** Attente des tâches non terminées....
Makefile.Release:22215 : la recette pour la cible « release/configdialog.o » a échouée
make[1]: *** [release/configdialog.o] Erreur 1
Makefile.Release:23212 : la recette pour la cible « release/diagramcontent.o » a échouée
make[1]: *** [release/diagramcontent.o] Erreur 1
Makefile.Release:21725 : la recette pour la cible « release/conductornumexport.o » a échouée
make[1]: *** [release/conductornumexport.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagram.cpp:18:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22806 : la recette pour la cible « release/diagram.o » a échouée
make[1]: *** [release/diagram.o] Erreur 1
In file included from ../sources/ui/titleblockpropertieswidget.h:23:0,
                 from ../sources/configpages.h:22,
                 from ../sources/configpages.cpp:19:
../sources/ui/../qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22397 : la recette pour la cible « release/configpages.o » a échouée
make[1]: *** [release/configpages.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcommands.h:27,
                 from ../sources/diagramcommands.cpp:18:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:23009 : la recette pour la cible « release/diagramcommands.o » a échouée
make[1]: *** [release/diagramcommands.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcommands.h:27,
                 from ../sources/diagramview.cpp:21:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:23671 : la recette pour la cible « release/diagramview.o » a échouée
make[1]: *** [release/diagramview.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/elementprovider.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:24049 : la recette pour la cible « release/elementprovider.o » a échouée
make[1]: *** [release/elementprovider.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/exportdialog.h:21,
                 from ../sources/createdxf.cpp:23:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/bordertitleblock.cpp:21:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22575 : la recette pour la cible « release/createdxf.o » a échouée
make[1]: *** [release/createdxf.o] Erreur 1
Makefile.Release:21315 : la recette pour la cible « release/bordertitleblock.o » a échouée
make[1]: *** [release/bordertitleblock.o] Erreur 1
make[1]: *** wait : Aucun processus enfant. Arrêt.
Makefile:42 : la recette pour la cible « release » a échouée           

Hmm .. fixed in the past but I don't remenber how I fixed this ..
https://qelectrotech.org/forum/viewtopi … 498#p13498
https://qelectrotech.org/forum/viewtopi … 140#p12140

Re: Nouveautés de la version de développement 0.8

@scorpio810 what is your cmake version?

cmake --version

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

For now I need found a solution for fix new KF5 KCoreAddons:
....

Hmm .. fixed in the past but I don't remenber how I fixed this ..
https://qelectrotech.org/forum/viewtopi … 498#p13498
https://qelectrotech.org/forum/viewtopi … 140#p12140

first you need to build KF5

mkdir -p ~/kde/src
cd ~/kde/src/
git clone https://invent.kde.org/sdk/kdesrc-build.git && cd kdesrc-build
./kdesrc-build --initial-setup
./kdesrc-build kwidgetsaddons karchive kcoreaddons --include-dependencies --ignore-modules Qt5

and that copy the following

cp ~/kde/usr/mkspecs/modules/*.pri ~/Qt/5.15.1/gcc_64/mkspecs/modules/
cp -r ~/kde/usr/include/* ~/Qt/5.15.2/gcc_64/include/
cp -r ~/kde/usr/lib64 ~/Qt/5.15.2/gcc_64/
cp -r ~/kde/usr/bin ~/Qt/5.15.2/gcc_64/

or where your QT is

Re: Nouveautés de la version de développement 0.8

Is 's run with KF5 5.70 and I use qmake
Same issue now on AppImage I have updated to Qt 5.15.2 yesterday with latest KF5 5.77.

https://download.tuxfamily.org/qet/forum_img_2/Screenshot_20201213_151514.png

288 (edited by De-Backer 2020-12-13 14:24:39)

Re: Nouveautés de la version de développement 0.8

i am trying with windows,
git clone  .....   why is it so slow

Could NOT find ECM

ECM (required version >= 5.70.0), Extra CMake Modules., <https://commits.kde.org/extra-cmake-modules>
CMake Error at C:/Program Files/CMake/share/cmake-3.19/Modules/FeatureSummary.cmake:457 (message):
  feature_summary() Error: REQUIRED package(s) are missing, aborting CMake

ok, so

 git clone https://github.com/KDE/extra-cmake-modules.git
mkdir build && cd build && cmake ..
-- Could NOT find Sphinx (missing: Sphinx_BUILD_EXECUTABLE) (Required is at least version "1.2")
-- Could NOT find ReuseTool (missing: REUSETOOL_EXECUTABLE) 
-- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter) 

ok, later Cmake will ask me to use linux instead of windows.

Re: Nouveautés de la version de développement 0.8

Maybe try on Linux like this:
https://qelectrotech.org/forum/viewtopi … 880#p10880

290 (edited by De-Backer 2020-12-13 15:51:41)

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

Maybe try on Linux like this:
https://qelectrotech.org/forum/viewtopi … 880#p10880

on linux it is no problem
but i wanted to see if it would work on windows without too many changes.
Building KF5 works in linux because it is a KDE version
but on windows, a disaster.
you essentially end up building a complete KDE and Python and Cmake and ReuseTool and Sphinx and qt and .... => it takes longer to build QET from code than to install linux on virtualbox and build it there!

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

For now I need found a solution for fix new KF5 KCoreAddons:

n file included from ../sources/diagram.h:27:0,
                 from ../sources/conductorautonumerotation.cpp:23:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcontent.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/ui/titleblockpropertieswidget.h:23:0,
                 from ../sources/configpages.h:22,
                 from ../sources/configdialog.cpp:20:
../sources/ui/../qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/conductornumexport.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:21538 : la recette pour la cible « release/conductorautonumerotation.o » a échouée
make[1]: *** [release/conductorautonumerotation.o] Erreur 1
make[1]: *** Attente des tâches non terminées....
Makefile.Release:22215 : la recette pour la cible « release/configdialog.o » a échouée
make[1]: *** [release/configdialog.o] Erreur 1
Makefile.Release:23212 : la recette pour la cible « release/diagramcontent.o » a échouée
make[1]: *** [release/diagramcontent.o] Erreur 1
Makefile.Release:21725 : la recette pour la cible « release/conductornumexport.o » a échouée
make[1]: *** [release/conductornumexport.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagram.cpp:18:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22806 : la recette pour la cible « release/diagram.o » a échouée
make[1]: *** [release/diagram.o] Erreur 1
In file included from ../sources/ui/titleblockpropertieswidget.h:23:0,
                 from ../sources/configpages.h:22,
                 from ../sources/configpages.cpp:19:
../sources/ui/../qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22397 : la recette pour la cible « release/configpages.o » a échouée
make[1]: *** [release/configpages.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcommands.h:27,
                 from ../sources/diagramcommands.cpp:18:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:23009 : la recette pour la cible « release/diagramcommands.o » a échouée
make[1]: *** [release/diagramcommands.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/diagramcommands.h:27,
                 from ../sources/diagramview.cpp:21:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:23671 : la recette pour la cible « release/diagramview.o » a échouée
make[1]: *** [release/diagramview.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/elementprovider.cpp:20:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:24049 : la recette pour la cible « release/elementprovider.o » a échouée
make[1]: *** [release/elementprovider.o] Erreur 1
In file included from ../sources/diagram.h:27:0,
                 from ../sources/exportdialog.h:21,
                 from ../sources/createdxf.cpp:23:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
In file included from ../sources/diagram.h:27:0,
                 from ../sources/bordertitleblock.cpp:21:
../sources/qetproject.h:31:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
 #include <KAutoSaveFile>
                         ^
compilation terminated.
Makefile.Release:22575 : la recette pour la cible « release/createdxf.o » a échouée
make[1]: *** [release/createdxf.o] Erreur 1
Makefile.Release:21315 : la recette pour la cible « release/bordertitleblock.o » a échouée
make[1]: *** [release/bordertitleblock.o] Erreur 1
make[1]: *** wait : Aucun processus enfant. Arrêt.
Makefile:42 : la recette pour la cible « release » a échouée           

Hmm .. fixed in the past but I don't remenber how I fixed this ..
https://qelectrotech.org/forum/viewtopi … 498#p13498
https://qelectrotech.org/forum/viewtopi … 140#p12140

Fixed :
https://invent.kde.org/sdk/kdesrc-build/-/issues/45

Re: Nouveautés de la version de développement 0.8

let me be clear, i'm not a fan of Cmake, it's new and difficult for me, but Cmake would give you a clear answer

eg

CMake Error at CMakeLists.txt:43 (include):
  include could not find load file:

    cmake/fetch_kdeaddon.cmake

Re: Nouveautés de la version de développement 0.8

De-Backer wrote:
scorpio810 wrote:

Maybe try on Linux like this:
https://qelectrotech.org/forum/viewtopi … 880#p10880

on linux it is no problem
but i wanted to see if it would work on windows without too many changes.
Building KF5 works in linux because it is a KDE version
but on windows, a disaster.
you essentially end up building a complete KDE and Python and Cmake and ReuseTool and Sphinx and qt and .... => it takes longer to build QET from code than to install linux on virtualbox and build it there!

You could try MXE with Digikam script like me to cross-compile QET for Windows.


https://mxe.cc/#requirements

git clone https://invent.kde.org/graphics/digikam.git
cd digikam/project/bundles/mxe/

1) I edit config.sh script for static build, but if you found a solution for shared build work.
2 ) edit 01-build-mxe.sh
I add sqlite and -j48 for make
and delete some package

3 ) run 01-build-mxe.sh

laurent@debian:~/digikam2/project/bundles/mxe$ ./01-build-mxe.sh 

It may take a while, several hours depending on the power of your machine

When finish edit 02-build-extralibs.sh and remove some packages not which not compile in static mode.

Run 02-build-extralibs.sh

laurent@debian:~/digikam2/project/bundles/mxe$ ./02-build-extralibs.sh 

If build ok, go to
cd /project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.static/mkspecs/modules/
and copy *.pri files to /project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.static/qt5/mkspecs/modules/

Since last KF5 change libs = $$PWD/../../lib I change path in these .pri files, like :

QT.KWidgetsAddons.VERSION = 5.77.0
QT.KWidgetsAddons.MAJOR_VERSION = 5
QT.KWidgetsAddons.MINOR_VERSION = 77
QT.KWidgetsAddons.PATCH_VERSION = 0
QT.KWidgetsAddons.name = KF5WidgetsAddons
QT.KWidgetsAddons.module = KF5WidgetsAddons
QT.KWidgetsAddons.defines =
QT.KWidgetsAddons.includes = /home/laurent/digikam3/project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.static/include/KF5/KWidgetsAddons
QT.KWidgetsAddons.private_includes =
QT.KWidgetsAddons.libs = /home/laurent/digikam3/project/bundles/mxe/build.win64/usr/x86_64-w64-mingw32.static/lib
QT.KWidgetsAddons.depends = widgets
QT.KWidgetsAddons.module_config = staticlib


Now edit again config.sh MXE_ARCHBITS 64 to 32
run again 01-build-mxe.sh and 02-build-extralibs.sh to cross-compil 32 bits env

Go to your /project/bundles/mxe/build.win32/usr/i686-w64-mingw32.static/mkspecs/modules/
edit path in yours *.pri files like

QT.KCoreAddons.VERSION = 5.77.0
QT.KCoreAddons.MAJOR_VERSION = 5
QT.KCoreAddons.MINOR_VERSION = 77
QT.KCoreAddons.PATCH_VERSION = 0
QT.KCoreAddons.name = KF5CoreAddons
QT.KCoreAddons.module = KF5CoreAddons
QT.KCoreAddons.defines =
QT.KCoreAddons.includes = /home/laurent/digikam3/project/bundles/mxe/build.win32/usr/i686-w64-mingw32.static/include/KF5/KCoreAddons
QT.KCoreAddons.private_includes =
QT.KCoreAddons.libs = /home/laurent/digikam3/project/bundles/mxe/build.win32/usr/i686-w64-mingw32.static/lib
QT.KCoreAddons.depends = core
QT.KCoreAddons.module_config = staticlib

and copy these to /project/bundles/mxe/build.win32/usr/i686-w64-mingw32.static/qt5/mkspecs/modules/

You can now test if QET cross-compile in 64 bits

git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror.git qet && cd qet
mkdir build && cd build
export PATH=/home/laurent/digikam2/project/bundles/mxe/build.win64/usr/bin:$PATH
/home/laurent/digikam2/project/bundles/mxe/build.win64/usr/bin/x86_64-w64-mingw32.static-qmake-qt5 ../qelectrotech.pro
time make -j48

For 32 bits :

rm -Rf build
mkdir build && cd build
export PATH=/home/laurent/digikam2/project/bundles/mxe/build.win32/usr/bin:$PATH
/home/laurent/digikam2/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.static-qmake-qt5 ../qelectrotech.pro 
time make -j48

If you are curious saw 03-build-digikam.sh for compile Digikam with shared libs

Post's attachments

Attachment icon 01-build-mxe.sh 5.79 kb, 76 downloads since 2020-12-16 

Attachment icon 02-build-extralibs.sh 5.92 kb, 75 downloads since 2020-12-16 

Attachment icon config.sh 2.63 kb, 74 downloads since 2020-12-16 

Attachment icon modules_32.tar.gz 1.2 kb, 71 downloads since 2020-12-16 

Attachment icon modules_64.tar.gz 1.16 kb, 73 downloads since 2020-12-16 

Re: Nouveautés de la version de développement 0.8

thanks laurent, i will try this too but on make -j15 and not make -j45
my PC is not a workstation.

Re: Nouveautés de la version de développement 0.8

La fibre aura durée 5 jours ... depuis vendredi dernier plus de réseau .... Orange ne peux pas intervenir sur les équipements SFR ...

Re: Nouveautés de la version de développement 0.8

scorpio810 wrote:

La fibre aura durée 5 jours ... depuis vendredi dernier plus de réseau .... Orange ne peux pas intervenir sur les équipements SFR ...

Not good news, what is the prediction / consequence for QET?

Re: Nouveautés de la version de développement 0.8

I 'm think not is an problem, I can use android tethering...like last year for sending my packages builds.

Re: Nouveautés de la version de développement 0.8

Retour sur la 4g.
SFR n'a pas de technicien ? (c'est une vrai question)

Re: Nouveautés de la version de développement 0.8

Joshua wrote:

Retour sur la 4g.
SFR n'a pas de technicien ? (c'est une vrai question)

Ma commune avait un contrat avec Orange, ils ont fibré une partie de la ville jusqu’à la fin du contrat et ça avançait vite et bien, SFR a gagné le marché mais suite a un litige entre les deux, les travaux ont repris après plus d'un an de procédure ..


Depuis le 19 décembre, je me bat au téléphone contre des robots, moulins .. Orange ne sachant pas ce qui se passe sur le terrain, on vous tiens au courant sans jamais rappeler ...la Scopelec oui on on rappellera demain matin sans faute... mais jamais personne ne rappelle ... C'est à croire que dans cette PMZ il n'y a pas de coupleurs Orange !! et qu'on prend les gens pour des cons ... et la guerre des opérateurs continue aux détriments des clients !!!!

Jusqu'au rétablissement de ma ligne je serai dans l'impossibilité de vous envoyer de nouveaux paquets, ni de continuer au développement de QET!

La 4 G ! une honte même pas 1Mb/s en descendant depuis 3 semaines sur antenne Orange  ... moins de 800 m  .... ..juste ok pour du surf léger, pensez pas travailler correctement avec ça...

A défaut je me suis remis à la lecture pour quelques semaines avec la saga Le Cycle des démons : ça m’évite l'envie de fracasser la livebox 5 a coup de masse ..
https://fr.wikipedia.org/wiki/Le_Cycle_des_d%C3%A9mons
https://booknode.com/serie/le-cycle-des-demons

300 (edited by De-Backer 2021-01-05 00:43:27)

Re: Nouveautés de la version de développement 0.8

https://media.tenor.com/images/b1c98908e2b1f6b2cdbad3ab98d60248/tenor.gif
I could not resist,nomicons/tongue
https://i.makeagif.com/media/4-12-2017/mpDkvK.gif
my brother in the 90's