From: Maurice Lombardi Newsgroups: comp.os.msdos.djgpp Subject: Re: OT: RHIDE and G77 (FORTRAN 77) Date: Wed, 17 May 2000 11:50:00 +0200 Organization: Universite Joseph Fourier - Grenoble 1 Lines: 83 Message-ID: <39226B48.A1EAB1B4@ujf-grenoble.fr> References: <391E8978 DOT 1E1DFF61 AT mtu-net DOT ru> <3921938A DOT 171A4DD5 AT ujf-grenoble DOT fr> <3921ACC4 DOT 70A633B3 AT mtu-net DOT ru> NNTP-Posting-Host: knautie.ujf-grenoble.fr Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: amazone.ujf-grenoble.fr 958557719 59094 193.54.234.27 (17 May 2000 10:01:59 GMT) X-Complaints-To: abus AT ujf-grenoble DOT fr NNTP-Posting-Date: 17 May 2000 10:01:59 GMT X-Mailer: Mozilla 4.7 [fr] (Win98; U) X-Accept-Language: fr,it,en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Alexei A. Frounze" a écrit : > > Yes, I checked that checkbox in RHIDE 1.4.7.5. Pascal source compiles to .O > but linker fails because by default libfpc.a file is specified. There is no > such a library file in FPC 0.99.12 (dos09912.zip). OOPs!!! It works only if I compile under rhide, but _without_ a project. I just start e.g. rhide mandel.pp and hit make or build after setting the "use FPC compiler" check box. If I create a project the usual way it indeed fails at linking for not finding libfpc.a This can be removed by setting RHIDE_TYPED_LIBS_FPC= either in djgpp.env or rhide.env but you stumble into other link errors. It seems that recent versions of fpc completely broke the rhide mechanism for compile_link. It you look into your directory after a broken compilation/link you see two files ppas.bat which calls the compiler and link.res which contains all the necessary linking information (directories and libraries) apparently rhide does not know about this mechanism and it is necesary to change other RHIDE_COMPILE_LINK..... lines to teach him what to do. Meanwhile since compiling without a project works I see little need to stumble into those intricacies. Anyway projects are needed for C C++ programming which cannot know where are the files it needs (what .c file contain the implementation for .h files it #include), but not for Pascal (either fpc or gpc) which determines everything it needs from uses clauses, not from a project, which in fact serves no purpose (except may be for setting up some default options, but these are contained in ppc386.cfg anyway). > -- > Alexei A. Frounze > ----------------------------------------- > Homepage: http://alexfru.chat.ru > Mirror: http://members.xoom.com/alexfru > > Maurice Lombardi wrote: > > > > "Alexei A. Frounze" a écrit : > > > > > > Btw, is there any person who has succeded to setup RHIDE for working with > > > FPC? > > > > > > It tries to link a program with fpc.a library although FPC has no such a > > > file. > > > > > Rhide 1.4.7.5 works for me. > > Have you set the option/environment/preferences/use FPC compiler > > checkbox ? > > > > -- > > Maurice Lombardi > > Laboratoire de Spectrometrie Physique, > > Universite Joseph Fourier de Grenoble, BP87 > > 38402 Saint Martin d'Heres Cedex FRANCE > > Tel: 33 (0)4 76 51 47 51 > > Fax: 33 (0)4 76 51 45 44 > > mailto:Maurice DOT Lombardi AT ujf-grenoble DOT fr -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice DOT Lombardi AT ujf-grenoble DOT fr