Sorry for a late response. If you still need help, here is some thoughts about your problem:
First of all, configure script is not a part of cross-compiler (code sourcery). If is a part of OpenCV distribution. Just go to the directory when you have installed opencv and it should be there. If it is not, you probably are using wrong distribution (for instance, Windows version does not have configure script, but Linux does).

Hope this helps.

Best regards,
Yuri

First of all thanks a lot for this great work.
I follow it step by step but it goes down when I want to configure.
At the line ./configure I get the error :no such file or directory.
I’m using arm-2009q3-67-arm-none-linux-gnueabi, which I installed on $HOME/CodeSourcery. I seek for the configure script and I can’t find it.

What can I do?

Thank you

That include error was a copy paste mistake.. Sorry for that. And yes I was using a UI but mistakenly copied a wrong test project.

I have built the project with carbon support. and will try porting it to the target.

Thanks a lot for your help …

Regards
Sagar

I am glad that my post has helped you in your work.

As for your questions, please read below:
First of all, the code you provided is not complete. I see “#include” without actual header you are including.
Next, you are writing that it falls while trying to execute “cvNamedWindow” function, but in your “main” function there is not such call.

In case you really trying to call cvNamedWindow – you are correct. If you build OpenCV without GTK/Carbon support there is no way for you to use any User Interface functions such as cvNamedWindow, cvShowImage, etc. You will have to rebuild OpenCV with GTK+ or Carbon support.

Another way to solve this problem it is to write corresponding wrapper functions, such as “myCvNamedWindow”, “myCvShowImage” and so on, and use them instead of standard “cvNamedWindow”, “cvShowImage”, etc. Inside these wrapper functions you may use any graphical framework (such as QT) available on your target platform to show what you need to show. By other words, you may create a new QT window in “myCvNamedWinodw” and display your image using QT API inside the “myCvShowImage” wrapper.

Hope this helps.

Best Regards,
Yuri Vashchenko

I Got tremendous help reading your posts and your article on crosscompilation of OpenCV for ARM9 platform. Thanks a lot for that.
For now I have successfully crosscompiled the OpenCV for ARM using all the info you have shared. There is a small problem.
I have used your shown configuration script during OpenCV build, without GTK and CARBON support.

Following was a small test code I was trying to compile for ARM 9 (Beagle board)

#include “cv.h”
#include “highgui.h”
#include “cxcore.h”
#include

int main()
{
printf(“\n\n This is a test program”);
IplImage * I = cvLoadImage(“test.bmp”,0);
cvSaveImage(“temp.bmp”,I);
exit(0);
}

Initial compile gave some errors but adding -pthread in the LDFLAGS variable in make solved them and generated the binary.

But when I tried to execute the binary on the Beagleboard I got the following errors

->
root@beagleboard:~# cd /media/mmcblk0p1/Sagar/
root@beagleboard:/media/mmcblk0p1/Sagar# ls
ARMscript.sh gmon.out makefile sapa temp.bmp test.cpp
root@beagleboard:/media/mmcblk0p1/Sagar# ./sapa

OpenCV ERROR: Unspecified error (The function is not implemented. Rebuild the library with Windows, GTK+ 2.x or Carbon support)
in function cvNamedWindow, window.cpp(71)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…
called from cvUnregisterType, cxpersistence.cpp(4933)
Terminating the application…

This is a test programroot@beagleboard:/media/mmcblk0p1/Sagar#
root@beagleboard:/media/mmcblk0p1/Sagar#

Now what I guessed from this is that as OPenCV was build without GTK CARBON support, the ARM was not able to include libraries used for GUI and Image load like highgui.lib.

Kindly tell me if my guess is right or not. If it is right please guide me in how do I resolve it.
I improvised by building the library using GTK support, but that generated a bunch of errors in the compile phase itself.

Kindly help .

Thanks and Regards
Sagar Joglekar

your last post has been very helpful….I successfully recompiled facedetect.c in Dec-C++ using this information…

thanx alot…

I am willing to help you, but I need more information.
As I understand, you are trying to compile some code that requires opencv and you are running Windows and Visual Studio 2008.
Do you need to make changes to existing opencv release or you just need to be able to use opencv library for your own applications?
If you do not need to do any changes to OpenCV library, the easiest way to start using opencv library is just to install it with provided installer (OpenCV_1.1pre1a.exe). When installed, you need to update your Visual Studio project properties to be able to compile your application.
First, you need to go to C/C++->General page and put paths to your opencv headers into “Additional Include Directories” field to make compiler know where to find them. It depends on where you have installed opencv, but by defaul it should read like “C:\Program Files\OpenCV\otherlibs\highgui”;”C:\Program Files\OpenCV\cxcore\include”;”C:\Program Files\OpenCV\cv\include”.
Next, you need to give linker directory on where to look for opencv libraries – go to Linker->General properties page and put the path into Additional Library Directories field. By default, the path is “C:\Program Files\OpenCV\lib”.
Finally, you need to say linker which libraries to use. Go to Linker->Input page and put “cv.lib cxcore.lib highgui.lib” (without quotes) into Additional Dependencies field. If you are using debug configuration, this should read “cvd.lib cxcored.lib highguid.lib” (without quotes)
That should make your application compile and run.
If not, you may want to send me your source code to look at. If I have it I can probably be more helpfull to you.

thankyou,

I am not sure I understand you question. What do you mean “compile individually cxcore”? What was the purpose of “hacking” the configure and makefile? Please clarify.
If you compiled the whole opencv, you already compiled cxcore, cv and cvaux. You can use generated libraries separately with your own applications.
If you ran the configure script, it should have generated Makefiles for all opencv compoinents. When you run Makefile, it first compiles cvcore, and even it fails (for any reason) later on other opencv components, it cxcore built successfully, you can use it separately. Next goes cv, then cvaux and finally, ml.
If you need opencv for a mulitiple platforms, you need a cross-compiler. Just give the “configure” script correct host, build and target platform names and it will generate you correct Makefiles. If your cross-compiler (I recommend you CodeSourcery G++ toolchain, they build gcc for different platforms) configured correctly everything should work, you do not need to modify your configure script or any Makefiles.

Thanks,
Yuri.