Re: Hard Floating Point Question

2013-02-16 Thread Christophe Lyon
>> - therefore, you should add ffmpeg to OpenCV, maybe using the 3rdparty >> directory, but I don't know how it is supposed to be used > > I too don't know. Then Cross compiling is not so simple like this: > > http://processors.wiki.ti.com/index.php/Building_OpenCV_for_ARM_Cortex-A8 > this does not

Re: Hard Floating Point Question

2013-02-15 Thread Zhenqiang Chen
On 4 February 2013 02:08, Matthew Gretton-Dann wrote: > On 2 February 2013 00:13, Derek Rollend wrote: >> Hello, >> >> I am currently trying to determine how much I can optimize OpenCV using the >> ARM's VFP and the Linaro nano image. I have downloaded the >> arm-linux-gnueabihf-gcc & arm-linux-

Re: Hard Floating Point Question

2013-02-15 Thread Fernan
>Christophe Lyon writes: > > Regarding your problems with ffmpeg, I'm sorry that I don't know how > cmake works, but after spending some time trying to understand why > cross-building fails, here are my remarks: > > - installing packages such as libavcodec-dev installs the version for > your

Re: Hard Floating Point Question

2013-02-12 Thread Christophe Lyon
I'd say that adding -L/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib is unnecessary as gcc's driver should be able to find its own libraries. Regarding your problems with ffmpeg, I'm sorry that I don't know how cmake works, but after spending some time tryin

Re: Hard Floating Point Question

2013-02-12 Thread Derek Rollend
I added the lib path explicitly so I knew that arm-linux-gnueabihf-g++ was definitely linking against the correct hard float libraries. Perhaps this is unnecessary, but I just wanted to be sure. I've been using OpenCV 2.2 because that was the version that was known to compile successfully from th

Re: Hard Floating Point Question

2013-02-12 Thread Fernan
Hi Derek, Derek Rollend writes: > > > Add the Linaro toolchain bin directory to your PATH environment variable: > export PATH="/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux >>/bin:$PATH" ok. I thought there was a CMake variable like CMAKE_C_COMPILER_PATH. I use this http://ww

Re: Hard Floating Point Question

2013-02-11 Thread Derek Rollend
Add the Linaro toolchain bin directory to your PATH environment variable: export PATH="/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/bin:$PATH" or whichever directory you have extracted the Linaro HF tarball to. -Derek On Mon, Feb 11, 2013 at 4:04 PM, Fernan wrote: > Derek

Re: Hard Floating Point Question

2013-02-11 Thread Fernan
Derek Rollend writes: > > > Fernan, > I'm using CMake 2.8.0.  I have not tried to compile OpenCV with FFMPEG support yet, although I will be trying to do this soon.  I have only successfully compiled OpenCV 2.2 using the Linaro hard float compiler.  Here is my toolchain.cmake file: > > > set(

Re: Hard Floating Point Question

2013-02-11 Thread Derek Rollend
Fernan, I'm using CMake 2.8.0. I have not tried to compile OpenCV with FFMPEG support yet, although I will be trying to do this soon. I have only successfully compiled OpenCV 2.2 using the Linaro hard float compiler. Here is my toolchain.cmake file: set( CMAKE_SYSTEM_NAME Linux ) set( CMAKE_SY

Re: Hard Floating Point Question

2013-02-11 Thread Fernan
Derek Rollend writes: > > Hello, > I am currently trying to determine how much I can optimize OpenCV using the >ARM's VFP and the Linaro nano image.  I have downloaded the >arm-linux-gnueabihf-gcc & arm-linux-gnueabihf-g++ compilers, successfully >cross-compiled OpenCV using those compilers (wit

Re: Hard Floating Point Question

2013-02-03 Thread Matthew Gretton-Dann
On 2 February 2013 00:13, Derek Rollend wrote: > Hello, > > I am currently trying to determine how much I can optimize OpenCV using the > ARM's VFP and the Linaro nano image. I have downloaded the > arm-linux-gnueabihf-gcc & arm-linux-gnueabihf-g++ compilers, successfully > cross-compiled OpenCV