ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
xiaohong has joined #mlpack
xiaohong has quit [Remote host closed the connection]
xiaohong has joined #mlpack
xiaohong has quit [Remote host closed the connection]
< kiwi_sreenik>
Nakul[m]: I hope you've figured it out already, however, if not, you can definitely compile with c++11 (I guess you are on Windows, which mean you'll probably have to enable it in the compiler options)
< Nakul[m]>
no i am using linux , i still struglling there is also mini projects and exams and all so i am not able to give much time
< rcurtin>
Nakul[m]: it is very tricky to compile an individual test with gcc... use cmake
ImQ009 has quit [Quit: Leaving]
HimanshuPathakGi has joined #mlpack
< HimanshuPathakGi>
Nakul: you can execute any individual file using g++ -g -O0 -o test your-test-file.cpp -Iinclude/ -Llib/ -lmlpack -larmadillo -I deps/stb/ -I deps/ensmallen-2.10.3/include/ -fopenmp
< HimanshuPathakGi>
and you should be inside the build directory on mlpack and after that
< HimanshuPathakGi>
(edited) and the last step ./test => $LD_LIBRARY_PATH=your path to mlpack-3.2.1/build/lib
< HimanshuPathakGi>
$ export LD_LIBRARY_PATH
< HimanshuPathakGi>
(edited) $LD_LIBRARY_PATH=your path to mlpack-3.2.1/build/lib
< HimanshuPathakGi>
$ export LD_LIBRARY_PATH => Nakul: you can execute any individual file using $ g++ -g -O0 -o test your-test-file.cpp -Iinclude/ -Llib/ -lmlpack -larmadillo -I deps/stb/ -I deps/ensmallen-2.10.3/include/ -fopenmp
< HimanshuPathakGi>
and you should be inside the build directory on mlpack and after that
< rcurtin>
HimanshuPathakGi: you're right, that does work, but I'd really recommend against building like that because it's quite brittle
< rcurtin>
it doesn't consider any of the preprocessor defines that CMake might have chosen to compile with
< rcurtin>
and requires libmlpack.so to be available and of the correct version, etc.
< rcurtin>
if it takes too long to just use 'make mlpack_test', my suggestion would be to comment out unnecessary tests in src/mlpack/tests/CMakeLists.txt
< rcurtin>
and if 'make mlpack_test' fails for some other reason, that should be debugged anyway (since any code being committed needs 'make mlpack_test' to succeed in order to be merged...)
< rcurtin>
plus, if 'make mlpack_test' fails, probably the custom g++ command is going to fail too
< rcurtin>
in any case, you're right that that particular g++ command does work now
< HimanshuPathakGi>
Thanks, rcurtin previously I was doing this. Next time I will try to comment out the unnecessary test to save time.
kiwi_sreenik has quit [Remote host closed the connection]
travis-ci has joined #mlpack
< travis-ci>
mlpack/mlpack#8357 (master - 2fc26e0 : Ryan Curtin): The build passed.