Compiled Gimp on Windows , it works but...

finally i managed to compile Gimp(2.6.6) on win (xp)
Result seems working with no issue but i am quite perplex about the architecture of the file system of what i got

To the point : the "lib" gimp folder is now in C:\MinGW\lib as the gimp "share" folder is in C:\MinGW\share and that looks right and logic :
is what i expected

But then gimp "bin" folder is NOT in C:\MinGW\bin as i would expect

There ,in MinGW/bin is well all the CONTENT of the gimp bin folder but is not enclosed in its own folder on the contrary is mixed with all the other executives already there.

Is that correct?...and if so how i am supposed to distinguish which belong to what i build from which was already there from before as part of MInGW?

And...If that is right why the MinGW bin directory has not the same architecture of the others MinGW directories ?(i quoted lib and share but is the same for the others...except for "bin") ?


_________________

> Von: "Alchemie foto\\\\grafiche" <fotocomics@yahoo.it>

> There ,in MinGW/bin is well all the CONTENT of the gimp bin folder but is
> not enclosed in its own folder on the contrary is mixed with all the other
> executives already there.
>
> Is that correct?

Yes. This is how it works on other platforms, where the file system layout is more strict than on Microsoft Windows.

If you do want to keep GIMP separate, you should pass the --prefix=drive:\any_path paramter to autogen.sh or configure.


For example, I use --prefix=c:/temp/gimp-2-6

for one of my builds.


HTH,
Michael

>> Is that correct?
>
>Yes. This is how it works on other platforms, where the file system layout
is more strict than on Microsoft Windows.
>
>If you do want to keep GIMP separate, you should pass the
--prefix=drive:\any_path paramter to autogen.sh or configure.
>
>
>For example, I use --prefix=c:/temp/gimp-2-6
>
>for one of my builds.
>
>
>HTH,
>Michael
>