Why don't they have a configure file in the source?
Can i create my own to compile them, and if so how?

As the purpose of configure is to produce a make file:

http://en.wikipedia.org/wiki/Configure_script

Then if the source code you've got already has a make file, then you may not need to run configure. Of course you may well have to edit the make file to fit your environment
The wiki page talks about using Autotools to create the configure.in file for configure.

Hy paynekj
you know how compile a plugin usually bundled in gimp ...i mean without have to compile all gimp ?
there is already a make file, but that suppose the plugin be compiled togheter with gimp

maybe a example may help

http://www.registry.gimp.org/files/gimpressionist.zip

This is exactly what i am talking about, compiling a plug-in outside of gimp. =)
I saw another tutorial out there on how to create your own makefiles.
Thanks for the wiki link paynekj!

Also, plugins compiled as a part of the gimp package are tied int he full gimp makefile and can't use those makefiles on their own.

Single c file externally developed plugins can be compiled using gimptool, which sets up all the other environment stuff. I've never seen someone take a built in plugin and compile outside the gimp tree successfully.

Another think to look at is the sample package provided in the gimp source:
http://git.gnome.org/browse/gimp-plugin-template/tree/

That may have the start you need to set up a makefile.

-Rob A>

but if they can't use they own makefile why often have one ?
as example this has its own make file included http://www.registry.gimp.org/files/map-object.zip
(that is identical to the original plugin folder as was in the source code, only exception the hardcoded value of the preview )

what the pourpose of a makefile that can't be used?
(hoping here that the answer is that can be used, but was needed some trick that i didn't know )

That's what i was hoping also .. lol
That i could drop in a command and vuala!

heheh .. i can see that just isn't going to happen now. =)

That makefile has a lot of upstream dependencies, and is designed to be called as a part of a larger make of the whole application. I don;t know enough about it to know what all must be set up first...

-Rob A>