After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 71514 - GUI / Functionality Separation
GUI / Functionality Separation
Product: GIMP
Classification: Other
Component: User Interface
Other All
: Normal enhancement
: 2.2
Assigned To: GIMP Bugs
Depends on:
Reported: 2002-02-14 19:52 UTC by carol
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description carol 2002-02-14 19:52:41 UTC
Both file scope wise and in use, particulary so that the GUI 
        version of the tool uses the pdb whenever possible
        (for finding bugs, and for macro recording)

        The core and the GUI have to reside in separate subdirectories.
Comment 1 Sven Neumann 2002-02-14 20:04:19 UTC
GUI/functionality separation actually one of the main goals for 1.4
and I think we've already come a long way towards it in the gimp-1.3
development tree.
Comment 2 Sven Neumann 2002-08-27 13:54:13 UTC
We are close to the point where you can build a version of The Gimp
that is not even linked to GTK+. Stay tuned.
Comment 3 Michael Natterer 2003-07-10 17:27:03 UTC
This will definitely happen soon in the 1.3 line.
Comment 4 Dave Neary 2003-07-26 10:32:49 UTC
What else need to happen before we can declare this feature request

Comment 5 Michael Natterer 2003-07-29 12:33:57 UTC
There needs to be a second toplevel makefile target which
creates a "gimp-console" binary that does not link against GTK+.
Comment 6 Dave Neary 2003-10-22 19:56:07 UTC
I was feeling brave last night and I had a look at this.

This seems very non-trivial. The auto* work is done, but many of the
files that are linked into gimp-console use gtk stuff. It's not a
monsteer job,, but I  don't think that it should be a blocker to 2.0.

Is there any opposition to bumping this (the actual creation of a
command-line app) to 2.2?

Comment 7 Sven Neumann 2003-10-23 00:12:28 UTC
I agree that this should be bumped to 2.2 The current gimp-1.3
executable already works completely w/o a other windowing system like
X11. Creating a binary that doesn't even link to gtk+ would of course
be elite but it's not a blocker.
Comment 8 Michael Natterer 2004-07-12 14:33:15 UTC
Fixed in CVS:

2004-07-12  Michael Natterer  <>

	Made the gimp-console binary compile.
	Finishes core/GUI separation and fixes bug #71514:

	* removed the crazy-hacker warning for

	* app/ for gimp-console, copy app_procs.c to
	app_procs_console.c and compile it instead of app_procs.c with

	* app/app_procs.[ch]: added some #ifndef GIMP_CONSOLE_COMPILATION
	to skip GUI stuff for the gimp-console case.
	Renamed app_gui_libs_init() to app_libs_init(), renamed
	app_gui_abort() to app_abort() and added app_exit() so everything
	that needs #ifdefs lives here now.

	* app/main.c: changed accordingly.

	* app/gui/gui.c (gui_abort): really abort (call exit()).