Where to find configuration parameters of official builds?

asked 2015-12-17 03:29:48 -0500

When using official build of OpenCV3 for Visual Studio 2012 (VC11 compiler), I got a bunch of linking errors. To resolve them, I compiled OpenCV3 from source using VC11 compiler. I didn't change any default parameters apart from turning off CUDA. My own build has no linking issues and my application works fine.

This makes me wondering, what might be the difference in official build and why it wasn't linking correctly. Building OpenCV from source was a hack to my current problem, but I would much rather change the configuration of my application and use the official build. It is simpler to distribute such program to clients. This leads to the question in the title.

edit retag flag offensive close merge delete

Comments

I bet your problem is just that you're using incorrect linkings paths in your VS property sheets. You need to use the proper paths to the bin and lib folders, and such paths are likely to be different in the pre-built packages than in your custom build (unless you make sure they're the same)

LorenaGdL gravatar imageLorenaGdL ( 2015-12-17 04:27:13 -0500 )edit

My project does not use property sheets. The paths to library are directly written in the project file. In for both cases these are linking to <opencv>build/x64/VC11/lib directory. After I compiled my library, I simply moved the official build to ../VC11.old/ and replaced it with my build.

Ekalic gravatar imageEkalic ( 2015-12-17 04:43:41 -0500 )edit

Not using property sheets seems like a really bad idea to me... People link and use official builds constantly, so I doubt there is any problem or difference, beyond using correct paths. Moreover, you say "I would much rather change the configuration of my application and use the official build. It is simpler to distribute such program", but in fact distribution is equal in both cases. Distribution does change when using static libs or dlls, but that has nothing to do with using pre-builts or building yourself

LorenaGdL gravatar imageLorenaGdL ( 2015-12-17 05:00:20 -0500 )edit

I said before. The path to lbs is equal in both builds. It works for my build, it doesn't work when on the same path is official build. When building OpenCV from source, CMake generates log that shows various flags used in the compilation. What I am asking for is this log that was generated when building official binaries. Additional details are as follows: I am building using Visual Studio 2015 bud using VC11 compiler. If this can be the reason..

Ekalic gravatar imageEkalic ( 2015-12-17 10:04:03 -0500 )edit

I don't get it. Are you compiling the libs using VC11 but then run your programs in VS2015? Why aren't you building the libs with VC14? And well, using pre-buils generated to be used with VC11, but then using them in VS15 are like gonna cause lots of trouble (more given the new features of Visual Studio 2015)

LorenaGdL gravatar imageLorenaGdL ( 2015-12-17 10:16:31 -0500 )edit

You want to ship VC11 build of your library. Don't worry, thanks for attention.

Ekalic gravatar imageEkalic ( 2015-12-17 10:18:58 -0500 )edit

My library? You're pretty wrong, I'm just another user (trying to help, btw...). I'm just saying that using VC11 pre-builts with VS2015 is not gonna work. If you had used the search bar of the forum, you would have found lots of topics about the issue, and also topics where users ask when pre-buils for VS2015 will be available. That's all. I also find your reasons to not build the library pretty non-sense like I said, but that's just my very personal opinion

LorenaGdL gravatar imageLorenaGdL ( 2015-12-17 10:23:30 -0500 )edit

I don't assume you are core developer of OpenCV.

Ekalic gravatar imageEkalic ( 2015-12-17 10:42:13 -0500 )edit