How to work with external libraries when cross compiling?

by

Regarding your general questions:

Why the C library works:

The C library is part of your cross toolchain. That’s why the headers are found and the program correctly links and runs. This is also true for some other very basic system libraries like libm and libstdc++ (not in every case, depends on the toolchain configuration).

In general when dealing with cross-development you need some way to get your desired libraries cross-compiled. Using binaries in this case is very rare. That is, especially with ARM hardware, because there are so many different configurations and often everything is stripped down much in different ways. That’s why binaries are not very much binary compatible between different devices and Linux configurations.

If you’re running Ubuntu on the Raspberry Pi then there is a chance that you may find a suitable ncurses library on the internet or even in some Ubuntu apt repository. The typical way, however, will be to cross compile the library with the specific toolchain you have got.

In cases when a lot and complex libraries need to be cross-compiled there are solutions that make life a bit easier like buildroot or ptxdist. These programs build complete Linux kernels and root file systems for embedded devices.

In your case, however, as long as you only want ncurses you can compile the source code yourself. You just need to download the sources, run configure while specifying your toolchain using the --host option. The --prefix option will choose the installation directory. After running make and make install, considering everything went fine, you will have got a set of headers and the ARM-compiled library for your application to link against.

Regarding cross compilation you will surely find loads of information on the internet and maybe ncurses has got some pointers in its shipped documentation, too.

More Related Contents:

  1. Hide password input on terminal
  2. Why does malloc initialize the values to 0 in gcc?
  3. Where is the header file on Linux? Why can’t I find ? [duplicate]
  4. Is there a way to use gcc to convert C to MIPS?
  5. Why does the C preprocessor interpret the word “linux” as the constant “1”?
  6. Merge multiple .so shared libraries
  7. How to include needed C library using gcc?
  8. What is the advantage of GCC’s __builtin_expect in if else statements?
  9. Finding out what the GCC include path is [duplicate]
  10. How to print the address of a function?
  11. `bash: ./a.out: No such file or directory` on running executable produced by `ld`
  12. Linking against older symbol version in a .so file
  13. Working of __asm__ __volatile__ (“” : : : “memory”)
  14. How to check if a given file descriptor stored in a variable is still valid?
  15. How to compile my own glibc C standard library from source and use it?
  16. Why am I able to perform floating point operations inside a Linux kernel module?
  17. Detecting 64bit compile in C
  18. Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
  19. Is there a macro definition to check the Linux kernel version?
  20. How to print time difference in accuracy of milliseconds and nanoseconds from C in Linux?
  21. How to trap unaligned memory access?
  22. GCC 4.7 Source Character Encoding and Execution Character Encoding For String Literals?
  23. calling assembly function from c
  24. Tool to analyze size of ELF sections and symbol
  25. How to flush the CPU cache for a region of address space in Linux?
  26. Process Linkage Table and Global Offset Table
  27. Returning struct containing array
  28. getrandom syscall in C not found
  29. How to print exact value of the program counter in C
  30. argv: Sanitizing wildcards

Leave a Comment