Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2011-02

Building a zip installer for cross-arm-linux

6 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Felipe Monteiro de Carvalho

Hello,

This is a continuation of the previous thread. In short, I am still trying to create a x86-linux -> arm-linux pre-compiled package.

Ok, so now I tryed following suggestions with this command:

make clean crossall crosszipinstall CPU_TARGET=arm OS_TARGET=linux NOWPOCYCLE=1 OPT="-dFPC_ARMEL" CROSSOPT="-CfSOFT"
BINUTILSPREFIX=arm-linux-

The binutils were installed with an RPM package, so they are on /usr/bin and I did the trick to substitute arm-linux-as with a shellscript which passes the mebi expected.

But the generated package has no executables! =o This command creates a tar.gz with two directories inside it:

bin -> empty
lib -> full with .o files

Some questions:

1> Any ideas why it creates an empty bin directory instead of putting there ppcarm?

2> What is NOWPOCYCLE=1 ?

3> What is CROSSOPT="-CfSOFT" ? This looks the same as OPT="-dFPC_ARMEL" ?

thanks,

Felipe Monteiro de Carvalho

Reply by email

Henry Vermaak
to Felipe Monteiro de Carvalho
Felipe Monteiro de Carvalho wrote 19 lines
Hello, This is a continuation of the previous thread. In short, I am still trying to create a x86-linux -> arm-linux pre-compiled package. Ok, so now I tryed following suggestions with this command: make clean crossall crosszipinstall CPU_TARGET=arm OS_TARGET=linux NOWPOCYCLE=1 OPT="-dFPC_ARMEL" CROSSOPT="-CfSOFT" BINUTILSPREFIX=arm-linux- The binutils were installed with an RPM package, so they are on /usr/bin and I did the trick to substitute arm-linux-as with a shellscript which passes the mebi expected. But the generated package has no executables! =o This command creates a tar.gz with two directories inside it: bin -> empty

Only the native tools will be installed there, so this will be empty on a crosszipinstall.

lib -> full with .o files

lib/fpc/2.5.1/ppcrossarm is the crosscompiler you are looking for.

Some questions: 1> Any ideas why it creates an empty bin directory instead of putting there ppcarm?

ppcarm is for native compilation, so if you want that, don't use crosszipinstall, just use zipinstall.

2> What is NOWPOCYCLE=1 ?

This is so that the compiler cycle doesn't do wpo (which adds another couple of cycles). I tend to use it because my computer is slow (and I am impatient). wpo should give better performance/size, though.

3> What is CROSSOPT="-CfSOFT" ? This looks the same as OPT="-dFPC_ARMEL" ?

This compiles the rtl/packages with -CfSOFT, which may be the default for an armel compiler, I'm not sure.

Henry

Reply by email

Felipe Monteiro de Carvalho
to Henry Vermaak
Henry Vermaak wrote
> lib -> full with .o files lib/fpc/2.5.1/ppcrossarm is the crosscompiler you are looking for.

Indeed =) In case this is useful for anyone, I managed to put full instructions about how to install this pre-compiled package which I have made:

http://wiki.lazarus.freepascal.org/Android_Interface#Using_the_pre-compiled_compiler

This package is targeted at writing Android apps, but I suppose it could be used for Meego and other arm-linux systems too.

thanks,

Felipe Monteiro de Carvalho

Reply by email

Felipe Monteiro de Carvalho
to Michael Schnell
Michael Schnell wrote
Will there be options to install the compiler and/or cross-compiler for/on

I am always working with cross-compilers. But of course you could try to install the standard FPC 2.4.2 into Android and try to run that somehow.

I suppose that if you install a shell program, an external keyboard and an external mouse you could get as productive as programming in a slow computer via the command line.

The main issue would be the lack of an IDE.

X86 Androids and on for/on the Android distribution for PC hardware ?

x86 Android is x86-linux. You don't really need anything special, your usual FPC and Lazarus installed via RPM or DEB should be more then enough to start writing x86-Android apps. Just build in your Linux desktop and package the project into a APK and it is now a x86-Android app.

Felipe Monteiro de Carvalho

Reply by email

Michael Schnell
to Felipe Monteiro de Carvalho

Sounds great.

I'll send the info to my son, who is doing some tests with the Android distribution that can be started on a PC (he is running same in Virtual Box).

Of course mouse and keyboard is not a problem with that installation. It's just provided out of the box.

Maybe on the long rung Lazarus might be made running on this....

-Michael

Reply by email