> How to cross compile fltk for ARM 9 platform . > > Could you please provide with step by step instruction to > follow to cross > compile .
You need to give us more information about your target platform. Saying it is Arm9 doesn't actually narrow it down all that much: - what operating system? I assume linux, but there are plenty of others possible (WinCE?, eCos? Etc...) - what graphics system and display go you have? - how much RAM? Storage? - what toolchain are you using? - etc. Anyway, I guess the "simple" case is if you have a board with a fair bit of RAM and storage, running linux (or an embedded version thereof) and X. Then, once you have your cross-compilation toolchain working (I assume you have that already - there are many options kicking around the web, and similarly many howto pages) and are able to compile simple test programs on your host then run them on your target, you proceed roughly as follows: - configure and compile fltk for your host (if you haven't done that already). - make a fltk tree for your cross-target builds. Into this, copy the config.h and makeinclude from your "host" tree. Now hand-edit these two files to specifically match the config of your cross-target. (This step is necessary because the fltk configure script is not fully cross-compilation aware, so will not correctly generate a cross-target build for you.) Edit config.h to describe the target setup (e.g. data sizes, openGL support, etc.) and edit makeinclude to set the paths and libs for your cross-compilation toolchain. However, some things (e.g. calls to fluid, for example) should call the host fluid, not the target fluid! - cd into the src directory. Make. - cd into the test directory. Make. - The generated test programs should now be copied onto your target, and tested. That should just about do it. If you are using a different operating system (e.g. ecos) then you wil have to port fltk, I think. There were patches circulating for fltk on winCE, but I'm not sure what happened to them. If you are running linux, but your display is not X, then again you will have to do some porting - there are nxlib ports of fltk around, but I have no helpful experience with using that. Framebuffer support or etc. does not exist yet AFAIK. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
