On 22 February 2015 at 11:02, Diego Roversi <[email protected]> wrote: > On Sat, 21 Feb 2015 15:51:19 +0200 > Siarhei Siamashka <[email protected]> wrote: > >> Regarding packaging, there are some pull requests on github, which try >> to add autotools support. I have quickly looked at these patches and did >> not quite like them. They add autogenerated files to git, which is not a >> great idea. And also they don't seem to really solve the problem of the >> need to use two toolchains at once (part of the build needs to be done >> by the compiler from the host machine, and part of the build needs to >> be done by an arm crosscompiler). > > In debian, packages are compiled with a native compiler on a native platform, > so it's not really a problem. BTW I think that adding autotools support to > trivial C program can be considere bike shedding (ihmo).
And any self-respecting distro has build time dependency handling so you don't really have to detect libraries since you will have them installed by the package build system. Everything except meminfo should work natively. I think meminfo should be built statically on arm as architecture:all package so you don't have to deal with cross-compiling at all. On the other hand, detecting a cross-compiler is a must if it is used because there does not seem to be a standard binary. eg. there is a 'gcc' package which installs some symlinks for the curreent version of gcc so that you can just run 'gcc' to compile C source but the situation for cross-compiler packages is less than ideal. Thanks Michal -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
