I am trying to use the MSER sample found in the samples directory of OpenCV 2.3.1.
At the moment the DLL missing error keeps popping up. This is the first time I am testing the MSER code and doubt that there is any dependency on TBB (Thread Building Block Routines).
Can I disable this dependency? Has anyone encountered this problem? I downloaded the OpenCV2.3.1 super pack today. And I am stuck on the very first sample I am testing.
Thanks for the guidance.
It is known "feature" of OpenCV 2.3.1 Windows package. The dll is really missing and you need to find it somewhere. The recent 2.4.0 beta has this dll.
Related
I am building a solution with CMake that uses wxWidgets. I have downloaded the source code for 3.1.0 and compiled it without issue. However, there are three libraries that my solution needs that are not in 3.1.0: dbgrid, mono, and odbc. I tried compiling 3.0.2, but VStudio 2015 will not compile the source code because it is outdated. I tried building 3.0.2 with GCC, but the Makefile was not recognized.
Any thoughts/suggestions on how I can build or find these three libraries, or build wxWidgets 3.0.2?
Thank you.
You should use the components with the same version known to work with your "solution". For example, use the same wxWidgets version that worked without issues.
On a more detailed note, ODBC component, including dbgrid, have been removed from anything later than wxWidgets 2.8; I have no idea what "mono" is but it doesn't sound like anything in wxWidgets. So going with any 3.x version is not going to help you. You might need to dig up version 2.8.12 from somewhere.
Also, for the sake of completeness, I have no idea what "the Makefile was not recognized" means, but GCC is a pretty reliable way of building wxWidgets, regardless the version of either of the two or the flavour of the former.
I have a ROS Indigo on a 64bit Kubuntu 14.04. Currently I'm facing a big issue - the missing module on_nurbs. I need it for the generation of meshes from point clouds.
My biggest problem here is the way ROS is hooked to PCL. Even though PCL is now more or less officially an external dependency the way ROS handles the situation is...Well, not very nice. I've experienced similar (maybe even the same - can't remember) issues with OpenCV - yet another dependency that was decided to be made completely external - when I decided to build it from source in order to add support Qt, OpenGL etc, which are not in the upstream packages of the library in the Ubuntu repositories. There is this thing ROS perception, which is supposed to add the glue between ROS and PCL.
The problem: Adding NURBS (part of the surface module)
What I have done so far:
I have
downloaded and built PCL 1.7.1 (the same version as the one shipped with Ubuntu 14.04 and ROS) with NURBS enabled
(1) installed PCL from source - ROS' PCL support broke
(2) replaced only the surface library (also added all the includes etc. dependencies for it and nurbs from my build) - ROS' PCL support broke
Currently I'm struggling to find out how to manually force CMake (and thus also catkin_make) to use my own version (not installed, only built). But I fear this will again interfere with ROS.
What is your advice for me in this situation? How can I proceed without yet again breaking my ROS installation? I would really like to learn how to add such missing bits and pieces - as mentioned above - I have already faced this issue once, now this and it will probably happen again.
PS for those who say "This is a ROS issue": I've already posted on ROS answers a week ago but there is still no reply and the views indicator of 11 (became so shortly after posting there - a week ago) is discouraging to say the least. The chances of any development there a week after posting the question are slim to none. I have been struggling with this issue for more then 2 weeks now...
I am working on old project in which i need to update code. The project also uses cocos 2d older version. When i build project with latest Xcode 6.0, it gives many errors. I tried the old way to integrate. I followed the steps given into Adding Cocos2D only to already existing project? not solves my problem. I am getting error like "Could not build module 'UIKit' " and many more similar error for other framework. So i decided to integrate new version of cocos 2d 3.1.0. Thanks in advance.
how to use monogame in platform not having directx 11? I tried installing the directx software on my machine but it still is giving some errors. Does anybody has any idea related to this?
Same problem was with me but i tried installing the mono again and the problem solved .Do try to install the older versions of the adirectx and sharpdx of old files .
I am not sure of the errors you are getting, but I would ask only how are you installing MonoGame?
The MonoGame guys have added an installer that helps to ensure that you get all the necessary files need to run MonoGame, as well as, install the base templates. You can find the MonoGame 3.0 installer here: http://monogame.codeplex.com/releases/view/96421
If you need more detail on installation, check out my tutorial here: http://blogs.msdn.com/b/tarawalker/archive/2012/12/04/windows-8-game-development-using-c-xna-and-monogame-3-0-building-a-shooter-game-walkthrough-part-1-overview-installation-monogame-3-0-project-creation.aspx
While changing the dojo version from 1.3 to 1.7.3, I simply replaced all my dojo 1.3 folder files with dojo 1.7.3. After rebuilding my web application, I am getting error hxrFailed at dojo.js, line no 15.
What is the wrong that I am facing here? Do I need to change any existing code. Is there any document to refer for all the required changes.
Please help me to get out from this issue.
Thanks,
Sridhar.ch
Lots changed and there are some lengthy tutorials to help you migrate. Check out the documentation tab on Dojo's website:
1.x to 2.0 migration guide:
http://dojotoolkit.org/reference-guide/1.8/releasenotes/migration-2.0.html
Updated buildsystem tutorial:
http://dojotoolkit.org/documentation/tutorials/1.8/build
In theory the current (1.8) build system is backward compatible until 2.0, but in practice I'm not sure it is 100% backward compatible because my 1.6 build profile didn't work with 1.7.x and up. I didn't try that hard to get it to work though.
I have gone through the same. the xhrFailed error occurred for me for multiple reasons. One of the reason was a missing a file in the define as below:
define(["something/was/missing/here"],function(){});.
Another cause for the same error occurred was when a folder in a path of a dependency was renamed but not updated in the application build profile. (This case only if your are doing custom builds).
See if that is the case!