GNOME Bugzilla – Bug 126000
GAP plug-ins don't like being moved
Last modified: 2004-12-22 21:47:04 UTC
When the GAP plug-in executables are moved to another directory (this is the default on win32 btw, since the files system is localized and users often install to arbitrary directories), strange things happen: Each time a GAP plug-in is used, a console windows opens. The plug-in itself seems to work, but most users will recognize it as broken. Some of them even seem to hang GIMP, but I've not been able to find a way reproduce this. Other GIMP plug-ins and GIMP itself can be moved without problems. Is anything hard coded in GAP that shouldn't be?
*** Bug 126499 has been marked as a duplicate of this bug. ***
Sorry, entered the number into the wrong entry. This report is unrelated.
It would certainly help if you could tell us what the console window is trying to tell us. I assume that there's some output, isn't it ?
IIRC there is no output, just the console window. "IIRC" because I don't have a working GAP right now, cause by the gimp_dialog_new changes.
You should be able to compile gimp-gap from CVS. Michael, can you check if the latest version still shows this problem?
Still happens with current cvs. The console windows open and close instantly when gimp is started, and stay open when the plug-ins are used in GIMP. But there is no ouput.
Are you sure this isn't just a case of missing -mwindows compiler flag?
As I get the same symptoms with the separate plug-in, and already successfully tried to add -mwindows to the LDFLAGS, this could be the cause here, too. So the fix would be to add this option. BTW, is there a reason why the console window does not appear when the plug-ins are not moved?
Closing this bug - -mwindows fixes it, and LDFLAGS get used.