[mlpack-git] [mlpack/mlpack] Windows 10 installation version (#613)
notifications at github.com
Wed Apr 13 13:17:14 EDT 2016
>I still don't understand why the errors were produced in Debug config.
Maybe you are mixing the libraries of debug build and release build, in the world of c++, debug and release library do not guarantee to provide same symbol and ABI, if you mixed them together, the best case is you can not compile your program, the worst case is it may generate subtle bugs from time to time, these bugs could make you scratch your head seriously if you do not know what was happen.
On windows, things become even more complicated(arggghhhh), your debug/release library need to link to correct runtime library, do not mixed them together if you do not want to spend several days, weeks even months to find out those evil bugs(I know a company confuse by those bugs more than 10 years, ridiculous?But this is true case).
Open your vc project, go to properties-.>C/C++->Code generation->Runtime library
There will be four types of library to choose
MD, MDd, MT, MTd
The library will small d means debug, without it means release, "M" mean multithread(old vc provide single thread lib, I think it is obsolete now)."D" mean dynamic, "T" mean static. If it is dynamic, that means you will need the dll come with vc if you want your program able to run, if it is static, that means you would not need them(but I haven't tried on this one, please correct me if I am wrong).
I think you are right, the meaning of ON is same as true. You would not need this if you compile the armadillo as static lib. Go to properties->General->Configuration type->set it to static library
This is same as adding macro definition in the project
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mlpack-git