In particular, it might be much easier to handle this: Click prefix => /usr/local/click Click temporary installation directory => /usr/local/click-cross/usr/local/click
than this: Click prefix => /usr/local/click Click temporary installation directory => /usr/local/click-cross Eddie On Wed, Nov 9, 2011 at 9:04 AM, Eddie Kohler <ekoh...@gmail.com> wrote: > Hi Sascha, > > Hmm. > > Can you tell me a bit more about your deployment situation?... Are you > installing with a DESTDIR, or copying the whole tree somewhere else? > It is not immediately clear to me how this should be handled. > > Eddie > > > On Tue, Nov 8, 2011 at 7:09 AM, Sascha Alexander Jopen > <jo...@informatik.uni-bonn.de> wrote: >> Hey, >> >> does anybody cross compile click packages? >> >> If i cross compile click with the default prefix, but install it to a >> different location for further usage with click packages, the file >> config.mk in clickdatadir contains the original prefix. This is fine to >> define the directories for the final destination locations of the >> packaged to be cross compiled, but the package Makefiles use this >> information to find the installed click instance, too. One can configure >> a package with --with-click=PREFIX, but this doesn't help. >> >> I know that i can compile click with local elements instead of packages, >> but using packages is a cleaner way, i think. >> >> Are there any special configure flags or something similar i am missing, >> to get click packages cross compiled? >> >> Regards, >> Sascha >> _______________________________________________ >> click mailing list >> click@amsterdam.lcs.mit.edu >> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >> > _______________________________________________ click mailing list click@amsterdam.lcs.mit.edu https://amsterdam.lcs.mit.edu/mailman/listinfo/click
