I am using VC++ 6. Don't ask why. It's just required.
My debug version is working fine. But release version was looking for a different version of OpenCV library and subsequently generated an error message "can't find cxcore100.dll" (correct one: 1.1, wrong one: 1.0) So I tried to find a reason while debugging it. So I set the "Generate Debug Info" in Link of Settings. When I run the release version, it does not generate the error message any more.
I don't think this is a good sign. What can be wrong here. Any guess or hint would be appreciated.
Then in the linker options for vc6 you are linking against cxcore100.lib in the release build and cxcore110.lib in the debug build. Just change them both to cxcore110.lib
ps although in more modern version of opencv there are separate release builds of the libs which end in 'd' - I don't remember what happened in v1
Related
I'm having a hard time building an executable from the example provided from https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/green_screen
I've tried using cmake GUI, VS 2017's cmake but to no avail. I'm not even sure how I should be installing OpenCV. Can anyone please help me?
That is very odd behaviour. I would suggest verifying that all the steps in the Building and Dependencies page are followed as described. As you can see is not just OpenCV. Please go through the list and verify you have all the required software.
~Pino
we made one application on Visual Studio 2008 , it about to release. but now we are getting the crash while launching the application . could you please any give a suggestion how do i debug on this particular issue
You can run the Release build in the debugger, too. Turn on debug-info settings in both the compiler and linker tabs (I think that was not the default in vs2008 and there were two distinct places to set) but don't change any optimization options or other setting.
Then launch the program from the debugger. If the resulting EXE shows the crash when run normally but not when started via the debugger, there are more things to make the situations work the same (and that shows clues as to what is wrong, too). So let us know if that still doesn't reproduce.
There could be a lot of reasons for your application's Release is crashing.
Did you link proper Release libraries with your application in Visual Studio project configuration ?
Check your code for some missing Release specific code.
My best guess is you are not linking to proper libraries for the Release version of your application.
Also, one reason could be that your application may be trying to load some file that may not exist. This happens with me sometimes when my Release build of application does not find file that it needs (Eg: OpenGL application trying to load a shader file that is missing); and you don't check for errors.
I'm getting the following error while building FireBreath Solution file .
The C Compiler Identification is unknown and
The CXX Compiler Identification is unknown
Can any one help me figuring out where am I doing wrong.
Note: 1) I have VS professional installed with c++ compilers and libraries
This may help
start visual-studio-2012 command prompt (e.g. Win64)
run cmake command with appropriate generator (e.g. -G "Visual Studio 12 Win64")
My research indicates that this is most likely a broken visual studio installation. You can try uninstalling / reinstalling, but if that doesn't work you might try making a new question that isn't tied to firebreath or plugins (which leads people to think they need to know something about firebreath or plugins to help you) and just asks about the error you're getting with cmake, since hte issue is actually that cmake isn't finding Visual Studio.
I have had this happen to me once before with VS2010 and to be honest I just ended up reinstalling the system. There is a thread about a similar issue where someone fixed it by copying an installation from another computer.
Other than that, I really have no idea.
I'm getting a compilation failure in IDEA 12 when trying to compile a Gradle project with the Groovy plugin installed and using Groovy version 2.1.3. The error I'm getting in IDEA that I don't see on the command line is here:
https://gist.github.com/jbrisbin/5416187
I'm using #CompileStatic in extension classes, if that's helpful.
Any ideas on workarounds?
Apparently when you create a new project in the latest versions of IDEA, the "external build" option is by default checked.
If you go into the settings and uncheck it [1], this error goes away (and the extremely excessive CPU usage goes away as well!).
Thanks to JetBrains support for the pointer.
[1] - http://img189.imageshack.us/img189/3550/20121206235318.png
I have been trying for days to debug into the c code of the sample hello-jni, with no success. I have installed all the requirements and followed many blog posts (repeating the process each time) to try to get this working.
I am using
Windows 7 64bit
Eclipse Juno with CDT 8.0.2
Android NDK r8b
Android SDK 20.0.3
the latest cygwin with make, gcc-core and gcc-g++ installed (altho I think NDK r8b doesn't need this?)
I have followed this
http://developer.android.com/tools/sdk/ndk/index.html
to set up and build the apk. It builds and installs fine and I can debug java code if launched as an Android Application
I followed this article about the NDK plugin
http://tools.android.com/recent/usingthendkplugin
but when launching as an Android Native Application with a breakpoint in the c code, the app launches and runs as normal with no breakpoint being hit and no error messages!
Any help would be greatly appreciated.
Thanks!
EDIT:
Here's some errors that appear in the console for half a second before being cleared
warning: while parsing target library list (at line 2): No segment defined for /system/bin/linker
warning: Could not load shared library symbols for 52 libraries, e.g. /system/bin/linker.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Quit (expect signal SIGINT when the program is resumed)
Turns out the above guides I used were all I needed and everything was working.
The warning messages were just... warnings and so debugging of the native code worked all along.
My problem was the native function call where I had my breakpoint was being called immediately - before the gdb could attach. I put the JNI function call into an onClick and found my breakpoint was being hit after all.
I hope the above links and this answer can help someone.
Thanks...
According to NDK documentation..
"At the moment 'ndk-gdb' requires a Unix shell to run. This means that
Cygwin is required to run it on Windows. We hope to get rid of this
limitation in a future NDK release."
JeffG are you able to debug native code on windows without cygwin?