Je comprends la volonté de limiter les DLL mais dans ce cas il faut tenir compte des évolutions de GIMP.
Pour la mise à jour de l’environnement vous pouvez essayer de forcer les choses par:
pacman -Syu --overwrite=’*’
Je joins les DLL que j’utilise qui proviennent d’un environnement à jour créé il y a 1 semaine, archive gmic_gimp_qt.7z .
Thank you for this update.
I tested the ‘zip’ version and there is no problem with GIMP-2.10.28 Win 64.
en français:
J’ai remarqué que les plugins QT n’étaient pas à jour (sous-répertoires). Ils se trouvent dans \msys64\mingw64\share\qt5\plugins
Avez-vous réussi à mettre à jour votre environnement msys2 ?
This morning I tested gmic_cli_win64.zip and gmic_qt_win64.zip (gmic_3.0.0_pre210919).
There is no problem with G’Mic CLI.
I can not record modified images in PNG format with G’MIC QT. This problem does not exist with the JPEG format.
With an old MSYS2 environment that is not updated regularly it is better to create a new one.
To go faster You can use existing packets in \msys64\var\cache\pacman\pkg\
I have installed GIMP 2.10.28 along with the latest GMIC 2.9.9 patch. here's the result (Win 10 64bit) installing GMIC 2.9.8 in GIMP 2.10.28 gives the same message
G`MIC 2.9.9 in GIMP 2.10.28 compilation samj works fine
I think it’s simply a problem of installation.
There is no patch but simply a new version of G’MIC (3.0.0_pre) to download and install.
Here is a method for succeeding:
You delete all the versions of G’MIC QT that you have,
Feature Request: Rectangle() function akin to polygon. Or maybe a way to define outline thickness and whether it’s inside polygon or middle or outside. See my G’MIC thread on the latest post to see why I want that. It’s a little harder to do stack polygon to create border. I think I like the second idea better now to think of it.
In G’MIC (not sure in Cimg / math interpreter - check yourself), rectangle is drawn by polygon. I would suggest you draw lines based on the coordinates you have. See linethick to investigate how to make lines have thickness.
For rectangle, to stimulate dilate in my use case, all I needed was to subtract, and then I made my recent filter 9 to 17.5 times faster. I’ll see how I can stimulate outline in the way I’m thinking of akin to Illustrator when I get to that though I think adding outline options would be much easier and less complicated.
Yes, that was what I was getting at. Follow the example of G’MIC in terms of the rectangle and thickline commands, using as many base functions as possible.
Linking gmic cli with latest opencv (4.5.4 from MacPorts) for “dc” and “apply_camera” there is a new error message from opencv, still it works. This is on MacOS 11.6. a git build of gmic cli.
gmic dc
[gmic]-0./ Start G’MIC interpreter.OpenCV: Couldn’t read video stream from file “check_opencv.mp4”
[gmic]-0./ Open camera stream viewer.
[gmic]-0./ End G’MIC interpreter.
During compilation there are lots of warnings, e.g.
In file included from gmic_cli.cpp:51:
In file included from ./gmic.h:247:
In file included from ./CImg.h:427:
In file included from /opt/local/include/opencv4/opencv2/opencv.hpp:52:
In file included from /opt/local/include/opencv4/opencv2/core.hpp:58:
/opt/local/include/opencv4/opencv2/core/mat.hpp:2504:5: warning: use of the ‘nodiscard’ attribute is a C++17 extension [-Wc++17-extensions]
CV_NODISCARD_STD static UMat eye(Size size, int type) { return eye(size, type, USAGE_DEFAULT); } // OpenCV 5.0: remove abi compatibility overload
^
/opt/local/include/opencv4/opencv2/core/cvdef.h:718:32: note: expanded from macro ‘CV_NODISCARD_STD’
# define CV_NODISCARD_STD [[nodiscard]]
^