[PD] compiling externals on ARM

[jo57]

I don't think it is clutter at all… I don't have one of these boards, but I'd love to try them, and when I do, I'd love to come back to this documentation...
Perhaps this could be added to the library template? 
http://puredata.info/docs/developer/LibraryTemplate
J

On Sep 9, 2013, at 11:39 AM, katja <katjavetter at gmail.com> wrote:

> Hi Ali,
> 
> Seems an interesting board, the Udoo. PengPod has Cortex-A8 while Udoo
> has Cortex-A9. But machine name is armv7l in both cases, meaning the
> same compiler flags may be used. If you want I can send you a project
> by private mail (don't want to clutter the list with this) which
> builds some home-brew externals and some externals from Pd-extended on
> RPi and PengPod amongst others. If it would build on Udoo too, we'd
> know a bit more.
> 
> Katja
> 
> On Mon, Sep 9, 2013 at 4:11 PM, Ali Momeni <batchku at gmail.com> wrote:
>> Hello,
>> Looks like the Udoo is the same as the PengPod.
>> Is the PengPod  something like:  http://pandaboard.org/
>> 
>> ?
>> 
>> 
>> Here's what i get:
>> 
>> ubuntu at imx6-qsdl:~$ uname -s
>> 
>> Linux
>> 
>> ubuntu at imx6-qsdl:~$ uname -a
>> 
>> Linux imx6-qsdl 3.0.35 #1 SMP PREEMPT Mon Aug 19 07:11:31 PDT 2013 armv7l
>> armv7l armv7l GNU/Linux
>> 
>> 
>> 
>> 
>> 
>> On Mon, Sep 9, 2013 at 10:03 AM, katja <katjavetter at gmail.com> wrote:
>>> 
>>> Hello Ali,
>>> 
>>> A while ago I've compiled home-brew Pd externals on Raspberry Pi and
>>> PengPod Linux tablet, and found that for each ARM processor type you
>>> can identify them by their proper name as returned by command uname
>>> -m. For RPi this is armv6l and for PengPod armv7l. So I could define
>>> individual flags for those ARM types in the makefiles.
>>> 
>>> There is no general approach to this, as makefiles in various Pd
>>> extended libs can be very different. In the template makefile which is
>>> used for many libs, the operating system is tested first with uname
>>> -s. If it is Linux, the processor type is found with uname -m and
>>> stored in variable CPU, which seems to be used for target 'showsetup'
>>> only, not for setting specific flags. Anyway, if you get "No rule to
>>> make target xxx.pd_linux" when trying to build a lib with template
>>> makefile, I wonder what you get from your Udoo board with command
>>> uname -s?
>>> 
>>> Katja
>>> 
>>> On Mon, Sep 9, 2013 at 2:06 PM, Ali Momeni <batchku at gmail.com> wrote:
>>>> 
>>>> 
>>>> hello all,
>>>> i'm working with a Udoo board (http://Udoo.org)
>>>> i've successfully compiled PureData 0.45 from miller's site;
>>>> i'm now trying to compile some of the externals in the pd svn, but i'm
>>>> getting the same error for all.
>>>> 
>>>> for instance, when trying to compile nusmuk-audio, i.e.
>>>> 
>>>> http://sourceforge.net/p/pure-data/svn/17203/tree/trunk/externals/nusmuk/nusmuk-audio/
>>>> 
>>>> i get the following
>>>> 
>>>>>>> ubuntu at imx6-qsdl:~/pd-externals/nusmuk/nusmuk-audio$ make
>>>> 
>>>>>>> make: * No rule to make target `bq~.pd_linux', needed by `all'.
>>>>>>> Stop.
>>>> 
>>>> I have contacted the developer (cyrille henry) and he adjusted the
>>>> MakeFile
>>>> to account for building for ARM; but i get the same error.  I notice,
>>>> incidentally, that i get the same error ("No rule to make target
>>>> xxx.pd_linux") for all other externals that i tried from the repository.
>>>> 
>>>> does anyone have any thoughts on how to resolve this?
>>>> 
>>>> 
>>>> thanks,
>>>> 
>>>> 
>>>> ali
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Pd-list at iem.at mailing list
>>>> UNSUBSCRIBE and account-management ->
>>>> http://lists.puredata.info/listinfo/pd-list
>>>> 
>> 
>> 
> 
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20130909/d9f38778/attachment.htm>