Re: [Gimp-developer] [Gegl-developer] Question abt compling GIMP

2006-11-30 Thread Michael Natterer
On Thu, 2006-11-30 at 00:14 +0800, howard chen wrote: On 11/29/06, Michael Natterer [EMAIL PROTECTED] 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`

Re: [Gimp-developer] [Gegl-developer] Question abt compling GIMP

2006-11-29 Thread Sven Neumann
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

Re: [Gimp-developer] [Gegl-developer] Question abt compling GIMP

2006-11-29 Thread Alexandre Prokoudine
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

Re: [Gimp-developer] [Gegl-developer] Question abt compling GIMP

2006-11-28 Thread Alexandre Prokoudine
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

Re: [Gimp-developer] [Gegl-developer] Question abt compling GIMP

2006-11-28 Thread Michael Natterer
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