[fpc-devel] Second version of FPC for iPhone SDK 2.x available

Jonas Maebe jonas.maebe at elis.ugent.be
Fri Mar 20 17:00:00 CET 2009

On 20 Mar 2009, at 16:46, dmitry boyarintsev wrote:

> i have a question: i'm using fpc trunk, so copmiled i386 units are not
> located at  /usr/local/lib/fpc/2.3.1/units/i386-darwin. Is there any
> way to reconfigure the building script, so compiled units are taken
> from the proper directory?

The easiest is to do a

sudo make install FPC=`pwd`/compiler/i386`

from the FPC directory after you've compiled a new FPC 2.3.1 version.  
You can always re-execute the /Developer/FreePascalCompiler/ 
finish_fpc_iphone_install.command script should you wish to reinstall  
the original compiler/units from the SDK.

The only side-effect of doing a "make install" is that the /usr/local/ 
bin/fpc binary will then default to FPC 2.3.1 instead of to your  
currently installed "stable" release (/usr/local/bin/ppc386 will not  
be changed though). If you want to prevent that, you can do this  
before the "make install":

cp /usr/local/bin/fpc .

and this after:

sudo mv fpc /usr/local/bin

> i guess, it's the reason, i'm getting compilation error:
> Compiling to /Users/igorkokarev/iPhoneFPC2/iphonetest2/build/ 
> iphonetest2.build/Debug-iphonesimulator/iphonetest2.build/ 
> DerivedSources-normal/i386
> Free Pascal Compiler version 2.3.1 [2008/10/27] for i386
> Copyright (c) 1993-2008 by Florian Klaempfl
> Target OS: Darwin for i386
> Compiling /Users/igorkokarev/iPhoneFPC2/iphonetest2/PascalLibrary.pas
> PPU Loading /usr/local/lib/fpc/2.3.1/units/i386-darwin//rtl/system.ppu
> PPU Invalid Version 95
> error: Can't find unit system used by PascalLibrary
> error: Compilation aborted


> sorry, I'm not much of XCode!

It's not Xcode-specific, but shell scripting. My scripts are not  
easily adaptable to a non-installed FPC, because then the layout of  
the unit directories is completely different (and I have to archive  
all object files belonging to the units in a static library for  
linking purposes, so it's not enough that the compiler can find the  


More information about the fpc-devel mailing list