[Click] Cross compile click packages

[Sascha Alexander Jopen]

In my case it's the easier deployment. In particular, i use the OpenWRT
buildroot for cross compilation of click packages. I install the
complete click "base package" with DESTDIR into a staging directory for
further usage.

So far i changed some definitions within the makefiles to use the click
build tools directly out of the source directory, because the installed
versions would be host binaries, not build system binaries. After fixing
the include directories and data directories i could compile two
different packages for userlevel. Neither linuxmodules nor bsdmodule
will work with the attached patch.
Im pretty sure this patch is not complete. I'm really new to such
"complex" makefiles. For example, no dependency files (*.d) are
generated for my packges, though this worked before.

Sascha

On 11/09/11 15:07, Eddie Kohler wrote:
> 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 <ekohler at 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
>> <jopen at 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 at amsterdam.lcs.mit.edu
>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>>
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: click-packages.patch
Type: text/x-patch
Size: 5675 bytes
Desc: not available
Url : http://amsterdam.lcs.mit.edu/pipermail/click/attachments/20111109/8d117623/attachment.bin