Hi Luigi, following your suggestions, i updated the patch [1] to support a toolchain root config and added 2 options to specify additional directories to search for header files and libraries.
I dropped the LD_LIBRARY_PATH hack as I'm not sure it's actually useful, but it could easily be added later if it proves it is. Thanks for your input 1. http://nico-and-co.net/void/patches/openwrt-r14393-external-toolchain-v4.diff Regards, -- Nico Luigi 'Comio' Mantellini wrote: > Hi Nico (Again! :D) > > > following the previous mail I think that also TOOLCHAIN_DIR directroy > should be fixed to TOOLCHAIN_ROOT value. > > > ciao > > > luigi > > > Il lunedì 02 febbraio 2009 18:18:15 Luigi 'Comio' Mantellini ha scritto: > > Hi Nico, > > > > I'm using your patch. I think that the user should give the following > > values: CONFIG_TOOLCHAIN_ROOT, the executalbes searching path > > CONFIG_TOOLCHAIN_COMPILER_PATH and the (target)libraries searching path > > CONFIG_TOOLCHAIN_LIBRARY_PATH > > > > The rules.mk should set COMPILER_PATH to > CONFIG_TOOLCHAIN_COMPILER_PATH and > > the LIBRARY_PATH to CONFIG_TOOLCHAIN_LIBRARY_PATH in order to have > compile. > > Of course all searching path should be fixed accordly. > > > > Other thing is that base-files should determinate the libraries to > copy on > > root fs using the $(CROSS_COMPILE)ldd tool > > > > I hope to give a contribute to have a stable external toolchain support. > > > > luigi > > > > Il venerdì 30 gennaio 2009 09:09:32 Luigi 'Comio' Mantellini ha scritto: > > > Hi Nico, > > > > > > thanks again for your patch. On my system works fine. > > > > > > best regards, > > > > > > luigi > > > > > > On Friday 30 January 2009 00:33:49 Nico wrote: > > > > Any objections committing the patch to trunk ? > > > > > > > > -- > > > > Nico > > > > > > > > Nico wrote: > > > > > Luigi 'Comio' Mantellini wrote: > > > > >> Thanks Nico, > > > > >> > > > > >> I will integrate asap on my experimental tree. I noticed a mistake > > > > >> > > > > >> row 262: > > > > >> > > > > >> + ifndef ($(CONFIG_NATIVE_TOOLCHAIN),) > > > > >> > > > > >> should be: > > > > >> > > > > >> + ifneq ($(CONFIG_NATIVE_TOOLCHAIN),) > > > > > > > > > > You're right, there was a couple of mistakes in my previous > patch. I > > > > > updated it [1]. > > > > > > > > > >> Anyway, it should be great if a toolchain prepared using > OpenWRT can > > > > >> be exported to others developers. > > > > > > > > > > Have you tried building the SDK? It should embed the toolchain (and > > > > > the set of files required to build packages). > > > > > > > > > > > > > > > 1. > > > > > > http://nico-and-co.net/void/patches/openwrt-r14216-external_toolchain > > > > >_v 3. diff > > > > > > > > > > -- > > > > > Nico > > > > > > > > > >> On Monday 26 January 2009 18:36:32 Nico wrote: > > > > >>> Hi Luigi, > > > > >>> > > > > >>> I have a patch [1] for external toolchains support, it will allow > > > > >>> you to select your target name (powerpc-unknow-linux-gnu), > > > > >>> toolchain commands prefix, toolchain binaries & libraries > path (for > > > > >>> toolchains installed in unusual locations and needing custom > PATH & > > > > >>> LD_LIBRARY_PATH). > > > > >>> > > > > >>> Let me know if it works for you :) > > > > >>> > > > > >>> 1. > > > > >>> > http://nico-and-co.net/void/patches/openwrt-r14204-external_toolcha > > > > >>>in .p atch > > > > >>> > > > > >>> -- > > > > >>> Nico > > > > >>> > > > > >>> Luigi 'Comio' Mantellini wrote: > > > > >>>> Hi ML, > > > > >>>> > > > > >>>> I need your help to understand the actual status of external > > > > >>>> toolchain support. > > > > >>>> > > > > >>>> In my environment, there are a lot of developers that works > on an > > > > >>>> building environment openwrt-based. Openwrt is a good choice to > > > > >>>> manage my builds and : I am happy to have chosen one year ago. > > > > >>>> > > > > >>>> The big problem that I observed is that OpenWRT doesn't > support in > > > > >>>> a clean-way the external toolchains. the NATIVE_TOOLCHAIN option > > > > >>>> seems to not resolve my problems because it disables > CROSS_COMPILE > > > > >>>> defines and I don't like the openwrt behaviour when this > option is > > > > >>>> enabled. > > > > >>>> > > > > >>>> I want understand if are there anybody that shares my > observation > > > > >>>> (or I'm not able to use native_toolchain in best way) and if a > > > > >>>> work on this topic can be appreciated by community. > > > > >>>> > > > > >>>> Kindly, give me any suggestion or opinion in order to understand > > > > >>>> what is needed to do and what I can do. > > > > >>>> > > > > >>>> thanks in advance, > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> luigi > > > > >>> > > > > >>> _______________________________________________ > > > > >>> openwrt-devel mailing list > > > > >>> openwrt-devel@lists.openwrt.org > > > > >>> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > > > > > > _______________________________________________ > > > > > openwrt-devel mailing list > > > > > openwrt-devel@lists.openwrt.org > > > > > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > > > > _______________________________________________ > > > > openwrt-devel mailing list > > > > openwrt-devel@lists.openwrt.org > > > > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > -- > Luigi Mantellini > R&D - Software > Industrie Dial Face S.p.A. > Via Canzo, 4 > 20068 Peschiera Borromeo (MI), Italy > Tel.: +39 02 5167 2813 > Fax: +39 02 5167 2459 > Email: luigi.mantell...@idf-hit.com > > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
