18:31 < Hieronymous> Hey, How do I "git clone" mlpack ?

18:32 < Hieronymous> I want to contribute (via PRs of course).

18:32 < rcurtin> git clone https://github.com/mlpack/mlpack is the command you'll need to use

18:32 < Hieronymous> okay and then build it with the normal instructions ?

18:32 < Hieronymous> I knew that btw

18:32 < rcurtin> yeah, the readme contains the instructions on how to build

18:33 < rcurtin> if you already knew that I am not sure why you asked, or maybe I answered the wrong question :)

18:34 < Hieronymous> My bad, I'm used to finding instructions that say - git clone something.. and then the specific build instructions.

18:34 < Hieronymous> mlpack didn't mention the git clone part in the README..so I thought maybe its different somehow. Never mind, its clear now.

18:34 < rcurtin> sounds good

18:35 < rcurtin> github has a link somewhere on each project's page for the clone URL

18:35 < Hieronymous> I know, its just that the README doesn't mention it, it says you can physically download the tarball and then build it.'

18:35 < Hieronymous> Not git clone the project and then build.

18:36 < Hieronymous> Even though both do just the same thing.

18:36 < rcurtin> note that the readme is what is distributed with a release, so it is written for that

18:37 < rcurtin> if you're cloning the git repository, it's not an actual release of the code

18:37 < Hieronymous> Yep, I'm aware. Its the "bleeding edge"

19:21 < Hieronymous> Hey, I was able to build mlpack successfully.

19:21 < Hieronymous> How do I test if it is installed ? Doing mlpack_knn --help causes a seg fault

19:21 < Hieronymous> Does that mean it isn't installed ?

19:22 < rcurtin> you need to set LD_LIBRARY_PATH to the directory containing libmlpack.so

19:22 < rcurtin> so if you built and didn't install, then this will be /path/to/mlpack/source/build/lib/

19:22 < rcurtin> if you did install, by default it'll be in /usr/local/lib/ so you can use that

19:23 < rcurtin> like $ LD_LIBRARY_PATH=/usr/local/lib/ mlpack_knn

19:23 < Hieronymous> Yeah I did run sudo make install in the end

19:24 < rcurtin> ok, then /usr/local/lib/ should work

19:24 < Hieronymous> It did :)

19:25 < rcurtin> ok, good to hear

19:26 < Hieronymous> I am used to compiling simple c++ programs the following way, g++ -o ./fi some_thing.cpp -std=c++11

19:26 < Hieronymous> But how do I compile a simple program in mlpack ?

19:27 < rcurtin> did you try the way you posted? :)

19:27 < Hieronymous> I see that there are different CLI arguments for each algorithm (from docs)

19:27 < Hieronymous> Yeah I did.

19:27 < rcurtin> and the result was?

19:27 < Hieronymous> I replaced something with a valid mlpack program.

19:27 < rcurtin> sure, of course

19:27 < Hieronymous> sample.cpp:(.text+0x356): undefined reference to `mlpack::CLI::ParseCommandLine(int, char**)'

19:27 < Hieronymous> Something like this, there are lot more like this.

19:28 < rcurtin> right, so you need to link against mlpack if you have undefined references

19:28 < rcurtin> and potentially other libraries depending

19:29 < Hieronymous> If I had to run the first program here - http://www.mlpack.org/docs/mlpack-2.0.3/doxygen.php?doc=sample.html ?

19:29 < Hieronymous> How would I do it via CLI ?

19:30 < Hieronymous> Thanks.

19:31 < rcurtin> did you link it successfully?

19:32 < rcurtin> if you did, did you just try to run the program?

19:32 < rcurtin> it's a regular C++ program...

19:33 < Hieronymous> I don't know how to link ? I'm sorry, my C++ knowledge is limited extremely limited.

19:33 < rcurtin> ok, sorry about that

19:34 < rcurtin> you'll link with -l<name of library>

19:34 < rcurtin> so -lmlpack

19:34 < rcurtin> and you may also need to link with some boost libraries like program options... -lboost_program_options

19:34 < rcurtin> once that's done you just run it from the command line, like if the program is named 'fi' you'd do './fi'

19:35 < Hieronymous> g++ -o -lmlpack ./fi sample.cpp -std=c++11 gives ./fi No such file or directory

19:37 < Hieronymous> I linked it in this fashion - g++ -o -lmlpack sample.cpp -o mlpack.so

19:37 < Hieronymous> It still throws a lot of errors.

19:38 < rcurtin> the -o option specifies the name of the output program

19:38 < rcurtin> so put the -lmlpack somewhere else, like at the end of the command

19:38 < rcurtin> I think you are telling g++ to name your program "-lmlpack" :)

19:38 < Hieronymous> lol :)

19:39 < rcurtin> I have to go for now, you might be better off finding a tutorial someone has written on compiling c++ programs from the command line or something like this to get some knowledge of how to do all this

19:39 < Hieronymous> Okay. Cool.

19:39 < rcurtin> probably it is easier to learn from them than from quick responses by me

23:02 < ikad> Hello

23:03 < ikad> How can I contribute to mlpack?