And with a normal installation if you delete that file it doesn't seem to affect the functionality of GIMP, so that's a no go there also. However, trying to dehardcode that file doesn't solve much. usr/bin/python=C:\Output\Gimp\GIMP 2\bin\pythonw.exe Python2=C:\Output\Gimp\GIMP 2\bin\pythonw.exe Python=C:\Output\Gimp\GIMP 2\bin\pythonw.exe I thought maybe it's some hardcoding in some files, the only thing i found it in pygimp.interp located in lib\gimp\2.0\interpreters: I am now curious what are the differences, i will try to do some more digging to see if maybe it's something that can be solved for the latest 2.10 releases also. I also changed the Application Folder to be in GIMP 2.Īnd after that, everything works! GIMP 2.8.22.0 works with MSIX! So again i've copied the dlls in System32 and System64. But of course i ran into the issues with the dlls that are not loading. I've deleted the files, doesn't seem to affect how it works. When you try to build it the first time you will receive some errors that GIMP 2\32\lib\gimp\2.0\python\' is not a valid Portable Executable for 'Build_MSIX_APPX->圆4' build and other 4 or 5. However, i've done more tests and i was thinking maybe something has changed since the 2.10 release of GIMP.and indeed something has changed. Kind tested 2.10.12 by creating the folder structure specified in their git board (C:\Output\Gimp) and installed it there (the path should be after installation C:\Output\Gimp\Gimp 2).Īfter that in the capture with Advanced Installer i specified the application folder to be GIMP 2, that solved for me the problem of copying the dlls to system32 and system64. To fix twain.exe to throw an error, you must also copy all the DLL files from 32\BIN to System32.Īfter that everything works correctly and applications starts/loads plugins. After the installation almost everything seems to work (99%), except twain.exe. I have made a capture of Gimp with Advanced Installer, and, without any redirections, i copied all the DLLs from the BIN folder in System64. System32 (C:\Windows\Syswow64) - For 32bit plugins Cree y edite gráficos y fotografías digitales con esta herramienta de edición gráfica de código abierto de primer nivel. System64 (C:\Windows\System32) - For 64bit pluginsĤ. The plugin directory (each plugin searches in its own directory)ģ. However, if we look closely in procmon, we can see that each and every plugin is searching for the DLL files in 3 directories:Ģ. When it calls to dlls it returns only buffer overflows. While the psf redirection works and the plugins then search in the correct directory, for whatever reason gimp.exe fails to start. If we check with procmon what is happening, after gimp is loaded, the plugins are searching for some DLLS in BIN. My question is what I should do to get this package working.Īny feedback is appreciated and with kind a workarround for this. When running the application the 'main' gimp-2.10.exe is started and is closed immediately. I created a new MSIX package and signed it. "workingDirectory": "VFS\\ProgramFilesX64\\GIMP 2\\bin" That file is located in VFS\ProgramFilesX64\GIMP 2\bin During the startup process, I get an error that the file cannot be found.After a while the application VFS\ProgramFilesX64\GIMP 2\lib\gimp\2.0\plug-ins\web-page\web-page.exe is started.VFS\ProgramFilesX64\GIMP 2\bin\gimp-2.10.exe is started.When running the application I get approximately 100 error messages that various. The source code, the Microsoft Windows installer and the Apple Disk Image for GIMP 2.8.I have created an MSIX from GIMP. On the Microsoft Windows platforms, crashes encountered when using the color picker with special multi-screen setups are gone, and picking the actual color instead of black from anywhere on the screen should finally be possible.Ĭheck out the full list of fixed issues since 2.8.20. Users on the Apple macOS platforms will benefit from fixes for crashes during drag
0 Comments
Leave a Reply. |