Jesse Vincent wrote:
> Two bugs you folks should be aware of before 2.0:
>
> To use ptxdist/OSELAS need gnu readlink (readlink -f), but you don't probe
> for it at
> configure time.
ACK, should be added
> For unspeakable reasons, I was running OSELAS Toolchain inside a path
> containing a spac
On Fri, Mar 27, 2009 at 12:32 AM, Robert Schwebel
wrote:
>> I just had a peek at the ptxdist doc again, e.g.
>> http://www.pengutronix.de/software/ptxdist/appnotes/AppNote_InstallingPtxdist.pdf
>> and was somewhat freaked out that all the examples used # as the
>> prompt. Is one expected to be roo
On Fri, Mar 27, 2009 at 12:55:51PM +0100, Jan Weitzel wrote:
> For me it works so. But i think not all options in ptxconfig are for
> all platforms the same. Like the gst-examples on a platform without
> camera interface.
Yup, will think about that.
rsc
--
Pengutronix e.K.
> The layout is right; what kind of sources are that?
A API library for the cortex-usb driver.
> > Can I make rules only selectable by special platforms and also locate
> > the sources in the platform folders?
>
> Hmm, not yet, but if that's a requirement (we havn't seen that for the
> first ti
ptxdist-boun...@pengutronix.de wrote on 27.03.2009 12:11:11:
>
> Its already part of the application note:
>
http://www.pengutronix.de/software/ptxdist/appnotes/AppNote_ExtendingMenu.pdf
>
Ok, i missed the jump from AppNote_WorkWithSources.pdf
"The last step is to activate this new rule file
On Freitag, 27. März 2009, Robert Schwebel wrote:
> On Fri, Mar 27, 2009 at 11:47:20AM +0100, Jan Weitzel wrote:
> > I want to integrate own sources in the OSELAS.BSP-Phytec-phyCORE-10
> > Bsp. The Sources are in the OSELAS.BSP-Phytec-phyCORE-10/local_src
> > and the rules (.make and .in) in OSELAS
Jan,
On Freitag, 27. März 2009, Jan Weitzel wrote:
> I want to integrate own sources in the OSELAS.BSP-Phytec-phyCORE-10 Bsp.
> The Sources are in the OSELAS.BSP-Phytec-phyCORE-10/local_src and the
> rules (.make and .in) in OSELAS.BSP-Phytec-phyCORE-10/rules.
>
> Where can I "activate" the rules
On Fri, Mar 27, 2009 at 11:47:20AM +0100, Jan Weitzel wrote:
> I want to integrate own sources in the OSELAS.BSP-Phytec-phyCORE-10
> Bsp. The Sources are in the OSELAS.BSP-Phytec-phyCORE-10/local_src
> and the rules (.make and .in) in OSELAS.BSP-Phytec-phyCORE-10/rules.
The layout is right; what k
Hello,
I want to integrate own sources in the OSELAS.BSP-Phytec-phyCORE-10 Bsp.
The Sources are in the OSELAS.BSP-Phytec-phyCORE-10/local_src and the
rules (.make and .in) in OSELAS.BSP-Phytec-phyCORE-10/rules.
Where can I "activate" the rules? I think this Info is missing in the
application no
Hello
I use PTXdist 1.99.12 and I try to compile
arm-v5te_vfp-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized
from OSELAS.Toolchain-1.99.3.1 and receive this error:
=
gcc -D__ARM_EABI__ rpc_sample.c -c -std=gnu99 -fgnu89-inline -O
Hi Dan,
On Thu, Mar 26, 2009 at 09:56:22PM -0700, Dan Kegel wrote:
> I just had a peek at the ptxdist doc again, e.g.
> http://www.pengutronix.de/software/ptxdist/appnotes/AppNote_InstallingPtxdist.pdf
> and was somewhat freaked out that all the examples used # as the
> prompt. Is one expected to
11 matches
Mail list logo