RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Question abt compling GIMP

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

5 of 7 messages available
Toggle history

Please log in to manage your subscriptions.
b66ddc900611281004t7da7bcb4... 07 Oct 20:24
  Question abt compling GIMP Alexandre Prokoudine 28 Nov 19:11
   Question abt compling GIMP Sven Neumann 29 Nov 10:35
    Question abt compling GIMP Alexandre Prokoudine 29 Nov 10:51
  Question abt compling GIMP Michael Natterer 28 Nov 19:42
b66ddc900611290813j5a2748ed... 07 Oct 20:24
  Question abt compling GIMP Michael Natterer 30 Nov 09:24
Alexandre Prokoudine
2006-11-28 19:11:40 UTC (almost 19 years ago)

Question abt compling GIMP

On 11/28/06, howard chen wrote:

I just want to modify a plugin file (*c) in the common folder, currently, when I modified the file, I use `make && make install` to compile, link and install the GIMP.

But this take some times to test the feature, are there any better method?

Make full compilation. Then, after, changing the plug-in file, remove relevant .o file and rerun 'make && make install' that will recompile the plugin again.

Alexandre

Michael Natterer
2006-11-28 19:42:08 UTC (almost 19 years ago)

Question abt compling GIMP

On Wed, 2006-11-29 at 02:04 +0800, howard chen wrote:

I just want to modify a plugin file (*c) in the common folder, currently, when I modified the file, I use `make && make install` to compile, link and install the GIMP.

But this take some times to test the feature, are there any better method?

Yes, you can say "make plugin" and "make install-plugin", you don't need to build and install the entire common/ folder each time.

ciao, --mitch

Sven Neumann
2006-11-29 10:35:34 UTC (almost 19 years ago)

Question abt compling GIMP

Hi,

On Tue, 2006-11-28 at 21:11 +0300, Alexandre Prokoudine wrote:

Make full compilation. Then, after, changing the plug-in file, remove relevant .o file and rerun 'make && make install' that will recompile the plugin again.

But this will take forever. Instead, say your plug-in is called foo.c, you can use 'make -C plug-ins/common foo' to build and 'make -C plug-ins/common install-foo' to install the plug-in. Unless you change the procedure registration, you don't even need to restart GIMP to test your changes.

Sven

Alexandre Prokoudine
2006-11-29 10:51:13 UTC (almost 19 years ago)

Question abt compling GIMP

On 11/29/06, Sven Neumann wrote:

But this will take forever. Instead, say your plug-in is called foo.c, you can use 'make -C plug-ins/common foo' to build and 'make -C plug-ins/common install-foo' to install the plug-in. Unless you change the procedure registration, you don't even need to restart GIMP to test your changes.

That's a very useful advice, thanx a lot!

Alexandre

Michael Natterer
2006-11-30 09:24:03 UTC (almost 19 years ago)

Question abt compling GIMP

On Thu, 2006-11-30 at 00:14 +0800, howard chen wrote:

On 11/29/06, Michael Natterer wrote:

On Wed, 2006-11-29 at 02:04 +0800, howard chen wrote:

I just want to modify a plugin file (*c) in the common folder, currently, when I modified the file, I use `make && make install` to compile, link and install the GIMP.

But this take some times to test the feature, are there any better method?

Yes, you can say "make plugin" and "make install-plugin", you don't need to build and install the entire common/ folder each time.

ciao, --mitch

i tried... but it said...

==> no rule to make target `plugin` stop

in fact, i can't find the target `plugin` in the Makefile

Of course "plugin" is just a placeholder, I suggest you use the name of the plugin you want to compile.

another question: how to print out some debug message in the GIMP program?

The same way you would add debugging in any other program.

ciao, --mitch