I am trying to compile Lazarus from source using a different compiler and I have hit a snag.
These are the steps followed so far, but I need to pass the path of the new fpc to the Lazarus make command. #create build and installation directories mkdir ~/LazarusBuilds mkdir ~/LazarusInstalls #fpc svn checkout http://svn.freepascal.org/svn/fpc/tags/release_2_4_0 fpc240 cd fpc240 make all PP=/usr/bin/fpc #use default fpc installed from Ubuntu package make install PP=/home/fchurch/LazarusBuilds/fpc240/compiler/ppc386 INSTALL_PREFIX=/home/fchurch/LazarusInstalls/fpc240 These are the issues I am having. 1. The fpc executable is installed in ~/LazarusInstalls/fpc240/bin/fpc When I execute ~/LazarusInstalls/fpc240/bin/fpc, the first 3 lines of output say: Free Pascal Compiler version 2.2.4-3 [2009/06/03] for i386 Copyright (c) 1993-2008 by Florian Klaempfl /usr/lib/fpc/2.2.4/ppc386 [options] <inputfile> [options] Obviously fpc calls ppc386 that is in the path, perhaps there is no fpc.cfg available. So how I can create an fpc.cfg and pass it the fpc I just compiled? Couldn't the install script create a suitable fpc.cfg to match the installation directory? 2. Onto Lazarus cd ~/LazarusBuilds svn checkout http://svn.freepascal.org/svn/lazarus/trunk lazarus27446 cd lazarus27446 make obviously fails here because I don't know the option of passing my shiny new fpc 2.4.0 to the make command. Is there an option for that, and are there other options to ensure that new compiler will only link with files from its subdirectories? There is also this hilarious bit in the README.txt that says. ================== Compilation: You don't need ./configure, just do []$ make clean all This will create the lazarus executable. Start it and enjoy. =================== What, doesn't even need FreePascal? There may be some legacy reasons why Lazarus/FPC doesn't use the ./configure approach, but at least a well documented bash script which allows you to set some variables before compilation would be very helpful. After all, the main idea of programming is never to use constants or literals where well documented variables will do /vfclists -- Frank Church ======================= http://devblog.brahmancreations.com
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
