Re: [gimpwin-users] Re: Can't Build the GIMP

Cyrille Grange <[email protected]>
Newsgroups gmane.comp.video.gimp.windows.devel
Message-ID <[email protected]>

Kevin Myers a écrit:

>Hi Cyrille -
>
>Thanks, that definitely helps.  I received your earlier message, but
>unfortunately didn't understand what you were trying to tell me.
>
I never send mail for you before, my previous mails was for my owns 
problems and solutions.

>
>Couple of questions to help reduce my confusion:  1) I thought that
>configure was supposed to detect MinGW and automatically pick up the
>Makefile.mingw?
>
if you want to use a specifique makefile in a specifique directory, you 
have to place in that directory and do : make -f makefile.mingw for 
example. By defaults, 'Makefile' are used.

>  2) If not, then I would have assumed that I just needed to
>completely replace the regular Makefile with Makefile.mingw, rather than
>only copying over specific chunks?
>
This did'nt work always for me, that's why i use this method.

>
>Any additional tips appreciated.  Thanks again.
>
Try looking for my (and others) previous mail in the ML, you will find 
tips to build Wingimp on Win32 with mingw (and cygwin).

Regards.

>
>s/KAM
>
>
>----- Original Message -----
>From: "Cyrille Grange" <[email protected]>
>To: <[email protected]>
>Sent: Tuesday, October 22, 2002 2:57 AM
>Subject: Re: [gimpwin-users] Re: [gimpwin-dev] Can't Build the GIMP
>
>
>  
>
>>Hi,
>>As explain in a previous mail, the only solution i found is to copy
>>rules from Makefile.mingw in the Makefile.
>>You have to copy the following rule from your Makefile.mingw :
>>
>>gimp_OBJECTS= ... (for me, without airbrush_blob.o and gradient_cmds.o)
>>gimp.exe : ...
>>gimp.exp : ...
>>
>>It was for the 1.2.3 winGimp Version (tml patched) with cygwin for the
>>bash and others tool and mingw32 for compilator and all on winNT machin.
>>
>>Good Luck ...
>>
>>
>>
>>Kevin Myers a écrit:
>>
>> >Arrrggghhhh!!!!  Yet another new and different problem.  After
>>everything in
>> >the app subdirectory is compiled, make stops after issuing the following
>> >message:
>> >
>> >make[2]: *** No rule to make target `gimp.def', needed by `gimp.exp'.
>>  Stop
>> >
>> >Any help appreciated.  I'm managing to get through this, slowly but
>> >surely...
>> >
>> >s/KAM
>> >
>> >
>> >----- Original Message -----
>> >From: "Kevin Myers" <[email protected]>
>> >To: <[email protected]>
>> >Cc: "gimpwin users" <[email protected]>
>> >Sent: Monday, October 21, 2002 8:09 PM
>> >Subject: Re: [gimpwin-dev] Can't Build the GIMP
>> >
>> >
>> >
>> >
>> >>I see now that it just also needed the path to gettext.  So, now I'm
>>    
>>
>past
>  
>
>> >>another sticking point.  Sorry for the extra email.
>> >>
>> >>
>> >>----- Original Message -----
>> >>From: "Kevin Myers" <[email protected]>
>> >>To: <[email protected]>
>> >>Cc: "gimpwin users" <[email protected]>
>> >>Sent: Monday, October 21, 2002 7:46 PM
>> >>Subject: Re: [gimpwin-dev] Can't Build the GIMP
>> >>
>> >>
>> >>
>> >>
>> >>>OK, I finally got the GIMP to start compiling.
>> >>>
>> >>>1. Had to comment out the lines in configure that were enabling
>> >>>the -fnative_struct (undocumented?) compiler flag.  Apparantly that is
>> >>>incompatible with the MinGW version of gcc that I downloaded (version
>> >>>
>> >>>
>> >3.2
>> >
>> >
>> >>>mingw special 20020817-1).
>> >>>
>> >>>2. Had to delete intl from the SUBDIRS variable in the top level
>> >>>
>> >>>
>> >Makefile.
>> >
>> >
>> >>>3. Had to change DATADIR to GDATDIR in the Makefile for libgimp and in
>> >>>gimpenv.c, because MinGW had a conflicting definition and use of
>>    
>>
>DATADIR
>  
>
>> >>>
>> >>>
>> >>in
>> >>
>> >>
>> >>>one of its windows related header files.
>> >>>
>> >>>But now I'm running in to another problem where gcc is executed with
>> >>>the -lintl option and ld complains that it can't find -lintl.  I have
>> >>>
>> >>>
>> >>tried
>> >>
>> >>
>> >>>supplying the appropriate path to the lib subdirectory of my libintl
>> >>>directory by using gcc's -L option.  I've tried using both MinGW and
>>    
>>
>dos
>  
>
>> >>>style paths.  Neither one seems to work.  Any ideas???
>> >>>
>> >>>s/KAM
>> >>>
>> >>>
>> >>>----- Original Message -----
>> >>>From: "Kevin Myers" <[email protected]>
>> >>>To: <[email protected]>
>> >>>Cc: "gimpwin users" <[email protected]>
>> >>>Sent: Monday, October 21, 2002 4:24 PM
>> >>>Subject: Re: [gimpwin-dev] Can't Build the GIMP
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>>Hi Tor and all,
>> >>>>
>> >>>>Thanks very much for your help.  Have made more progress.  Figured
>>    
>>
>out
>  
>
>> >>>>
>> >>>>
>> >>>that
>> >>>
>> >>>
>> >>>>I didn't need to copy pkg-config to gnome-config after all, as Tor
>> >>>>
>> >>>>
>> >>>mentioned
>> >>>
>> >>>
>> >>>>below.  Also, found the LIBTIFF, LIBJPEG, LIGPNG, LIBZ, and LIBICONV
>> >>>>environment variables, which allow me to point configure to the
>> >>>>
>> >>>>
>> >correct
>> >
>> >
>> >>>>locations for those libraries.  Now have yet another problem.
>> >>>>
>> >>>>
>> >configure
>> >
>> >
>> >>>>quits after spitting out the following error message:
>> >>>>
>> >>>>config.status: error: cannot find input file:
>> >>>>
>> >>>>
>> >plug-ins/perl/config.pl.in
>> >
>> >
>> >>>>Like it says, the subject file does not exist in Tor's gimp source
>> >>>>distribution which I downloaded.  How can I go about correcting this
>> >>>>problem?  BTW, I tried the --disable-perl option, and that didn't
>>    
>>
>seem
>  
>
>> >>>>
>> >>>>
>> >>to
>> >>
>> >>
>> >>>>help.  configure still choked at the same point.
>> >>>>
>> >>>>Thanks again.
>> >>>>
>> >>>>s/KAM
>> >>>>
>> >>>>
>> >>>>----- Original Message -----
>> >>>>From: "Tor Lillqvist" <[email protected]>
>> >>>>To: <[email protected]>
>> >>>>Cc: "gimpwin users" <[email protected]>
>> >>>>Sent: Monday, October 21, 2002 4:06 PM
>> >>>>Subject: Re: [gimpwin-dev] Can't Build the GIMP
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>>Kevin Myers writes:
>> >>>>> > I had to copy pkg-config.exe to gnome-config.exe (apparantly
>> >>>>>
>> >>>>>
>> >there
>> >
>> >
>> >>is
>> >>
>> >>
>> >>>>still
>> >>>>
>> >>>>
>> >>>>> > somewhere within the pkg-config 0.13 source code that it is
>> >>>>>
>> >>>>>
>> >>refering
>> >>
>> >>
>> >>>to
>> >>>
>> >>>
>> >>>>> > itself by the old gnome-config name),
>> >>>>>
>> >>>>>Nah, that shouldn't be necessary or useful (other than to shut up
>> >>>>>
>> >>>>>
>> >the
>> >
>> >
>> >>>>>silly misleading messages).
>> >>>>>
>> >>>>> > Now the next problem seems to be that configure can't find
>> >>>>>
>> >>>>>
>> >libtiff.
>> >
>> >
>> >>>My
>> >>>
>> >>>
>> >>>>> > tiff-3.5.7-lib directory is at the same level as my gimp-1.2.4
>> >>>>>
>> >>>>>
>> >>>>directory.
>> >>>>
>> >>>>
>> >>>>> > How do I tell configure where it should be looking to find
>> >>>>>
>> >>>>>
>> >libtiff?
>> >
>> >
>> >>>>>With the CPPFLAGS and LDFLAGS environment variables? As in:
>> >>>>>
>> >>>>>CC='gcc -mpentiumpro' CPPFLAGS='-I/where/ever/include -I...'
>> >>>>>
>> >>>>>
>> >>>>LDFLAGS='-L/where/ever/lib -L...'
>> >>>>
>> >>>>
>> >>>>
>> >./configure --disable-static --disable-perl --disable-print
>>--prefix=/some/w
>> >
>> >
>> >>>>here ...
>> >>>>
>> >>>>
>> >>>>>--tml
>> >>>>>
>> >>>>>
>> >>>>>
>> >
>> >
>> >
>> >List archives: <http://groups.yahoo.com/group/gimpwin-users/>
>> >To unsubscribe send a blank message from the address you're subscribed
>> >to <mailto:[email protected]>
>> >
>> >Your use of Yahoo! Groups is subject to
>>    
>>
>http://docs.yahoo.com/info/terms/
>  
>
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>>
>>
>>To Post a message, send it to:   [email protected]
>>To Unsubscribe, send a blank message to:
>>    
>>
>[email protected]
>  
>
>>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>>
>>
>>    
>>
>
>
>
>To Post a message, send it to:   [email protected]
>To Unsubscribe, send a blank message to: [email protected] 
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
>
>
>
>  
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.