On Fri, 10 Nov 2017 17:47:11 +0100 Marc Santhoff <m.santh...@web.de> wrote:
> Hi again, > > (too many sub threads, answering here - thanks to all helpers!) > > OK, "$FPC -va | grep CPU" does the trick. If using the ppcrossarm: > > marc@puma:/home/marc/program/fpc-cross/src/fpc/compiler > ./ppcrossarm > -va|grep CPU > [0.004] Macro defined: CPUARMEL > [0.004] Macro defined: FPC_CPUCROSSCOMPILING > [0.004] Macro defined: CPUARM > [0.004] Macro defined: CPU32 > [0.004] Macro defined: CPUINT32 > [0.020] interpreting file option "#IFNDEF CPUI386" > [0.020] interpreting file option "#IFNDEF CPUAMD64" > > See, an arm compiler. But when using the ppc binary in the same dir it > looks different. Here we go: > > marc@puma:/home/marc/program/fpc-cross/src/fpc/compiler > ./ppc -va | grep CPU What is ppc? Where is fpc? > Next question is how to get started with lazarus and multiple compilers. > How do you do it, using configuration files for lazarus and starting > like "lazarus --primary-config-path= <path>"? Or are there other > possibilities to try? Lazarus supports multiple compilers. You can either use fpc and switch the target OS and /or processor. Or you can switch the compiler binary: Project / Project Options / Compiler Options / Compiler Command. Replace the default value '$(CompPath)' with the path. You can use build modes to switch with a mouse click between various sets of compiler options. Mattias _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
