08:31 < tham> uzipaz : I can build mlpack on windows8.1 64bits with msvc2015 64bits

08:33 < tham> you can see my blog(http://qtandopencv.blogspot.my/2015/09/deep-learning-04-compile-mlpack-1012-on.html) if you are interested how to build it step by step

08:33 < tham> You do not need libxml2, iconv and zlib but armadillo, lapack, openblas and boost

08:34 < tham> You do not need to build boost by yourself, the community already build it for you, just download

08:37 < tham> I do not know why you cannot find openMP yet(it works well on vc2013, vc2015)

08:37 < tham> but the problems of cannot find boost root is easy to solve

08:41 < tham> you can specify the path in your CMakeLists.txt, as my blog and issues #613 show

08:42 < tham> issues #613 has a lot of informations about how to compile mlpack on windows, maybe it could help you

11:02 < zoq> tham: Do you think it's a good idea to provide a visual studio project file bundled with all precompiled dependencies?

11:03 < tham> zoq : it would be nice if someone want to do that

11:03 < tham> By now, the compiler need to support on windows are vc2015 32,64 and mingw 32,64

11:04 < tham> or you prefer to support vc2015 only?

11:04 < tham> I can try to provide prebuild version of vc2015 64 to nuget

11:05 < tham> but I think it would be better if the publisher is come from the admin of mlpack, it looks safer

11:06 < tham> because, well, some publisher may inject some evil codes into the libraries

11:07 < tham> the uers may not trust it if the publisher is nobody

11:08 < tham> If we really want to provide a precompiled version, we need to determine which versions of boost, armadillo, openBLAS and Lapack we like to provide too

11:09 < tham> Other solution is, maybe like opencv

11:09 < tham> download necessary dependencies from the network when the users try to build it

11:11 < zoq> tham: I wasn't thinking about a nuget pakage, I think we could make the build process on windows a lot easier if we would provide all the precompiled dependeciens, and an already configureted msvs project file. So the only thing left is to open up msvs or the command line and to press build or make to build mlpack.

11:14 < tham> I think this could be done

11:15 < tham> But it also lack some flexibility

11:16 < tham> How could user update their vc project file?

11:17 < tham> The codes mlpack keep changing, but it do not release the stable version frequently

11:17 < tham> When the users want to try out the new features, they still need to pull it from github

11:18 < tham> Maybe we could provide all the precompiled dependencies on the server

11:19 < zoq> tham: And then you have to reconfigure the project file, right.

11:19 < tham> When the users use cmake to generate their vc project file, we could download those dependencies to their pc

11:21 < zoq> tham: You can already download the precompiled dependencies: https://ci.appveyor.com/project/mlpack/mlpack/build/artifacts

11:23 < zoq> tham: I was thinking about how we could streamline the windows build process, one way would be to provide a ms vs project file, but you are right, you need to update the project file once, you add something.

11:26 < zoq> Maybe the process is already streamlined, at the end all you need to do is to download the precompiled dependencies and run:

11:26 < zoq> cmake -G "Visual Studio 14 2015 Win64" -DBLAS_LIBRARY:FILEPATH="libopenblas.dll.a" -DLAPACK_LIBRARY:FILEPATH="libopenblas.dll.a" -DARMADILLO_INCLUDE_DIR="C:/projects/mlpack/armadillo-6.500.5/include" -DARMADILLO_LIBRARY:FILEPATH="C:\projects\mlpack\armadillo-6.500.5\build\Debug\armadillo.lib" -DBOOST_INCLUDEDIR:PATH="C:\projects\mlpack\boost.1.60.0.0\lib\native\include" -DBOOST_LIBRARYDIR:PATH="C:\projects\mlp

11:26 < zoq> ack\boost_libs" -DDEBUG=OFF -DPROFILE=OFF ..

11:58 < tham> zoq : sorry, I did not notice I was disconnected

12:00 < tham> I think it is a good idea, either automate the download process by cmake

12:01 < tham> or write on the document, tell the users where to download the precompiled libs, where should them place the precompiled libs

12:01 < tham> write in I think

12:08 < tham> I prefer automate the download process by cmake

12:09 < tham> But some users may build their libs already, this would make them download the dependencies libs two times

13:14 < zoq> tham: I'm not sure integrating the windows build process using cmake is the right way here, since that's only one way to build mlpack on windows

13:25 < rcurtin> would a better solution be to provide a precompiled mlpack installation for windows?

13:26 < rcurtin> I think this has been talked about before, and I was supposed to set up the windows build slave so we could finish it, but I have been busy with other things... :(

13:29 < zoq> I agree providing a precompiled mlpack for windows is a good, the appveyor build should do that already, however I was thinking about how we could streamline the build process, if someone likes to contribute.

13:31 < zoq> I guess, we could also provide a VM image :)

13:32 < tham> zoq : what do you mean "integrating the windows build process using cmake is the right way here"?Do you mean should not automate download process or should not rely on cmake?

13:33 < tham> Like a VM image of ubuntu?

13:33 < Guest26408> #gsoc

13:34 < zoq> tham: The download process ... CMake should be able to detect all the necessary dependencies.

13:36 < tham> Then we could setup default dependencies path by cmake(also provide users the choice to change them from gui, command line)

13:37 < tham> Tell them where could they find the prebuild binary and place them

13:38 < tham> A prebuild package is good, but less flexiblity, I think it would be easier to attract contributors if they find mlpack easy to build

13:39 < tham> and users

13:42 < zoq> tham: There is already an default path for the windows build e.g. "C:/Program Files/Armadillo"

13:42 < zoq> tham: I agree, we can add some pointers where to dowload the dependencies, etc.

13:49 < zoq> Also, I guess we could also provide some kind of build script that does everything for you.

13:56 < tham> zoq : Do you mean, the script should be able to download necessary dependencies, unzip them, put them in the right place?

14:10 < zoq> tham: yeah or use some installer

14:11 < zoq> something like: https://github.com/thirdwing/mlpack/commit/bfe4e9c7876c1198b5dde4df635017013aeded73#commitcomment-9249007

14:22 < tham> The task of the installer are

14:22 < tham> 1 : download neccessary dependencies

14:22 < tham> 2 : place them at correct path

14:23 < tham> That means the users only need to

14:23 < tham> 1 : pull mlpack from github

14:23 < tham> 2 : execute the installer

14:24 < tham> 3 : run cmake

14:24 < tham> 4 : compile mlpack by vc

14:49 < zoq> tham: right

15:13 < tham> zoq : I think this is a good idea

15:14 < tham> could you make sure the link of the dependencies are fixed?

15:14 < tham> Or the installer should be able to read the link from somewhere?

15:15 < tham> I need to go to bed now, see you tomorrow

16:04 < uzipaz> zoq: I spent the whole yesterday trying to install all the dependencies Mingw/msys, openblas, lapack, boost from source... I run cmake on mlpack but I cannot find boost libraries, I downloaded the boost source, and used bootstrap and b2 to build boost, I am not sure where I am supposed to specify a path to Boost_root or its include, lib directories, can anyone help me with that?

16:04 < uzipaz> rcurtin:

16:08 < zoq> uzipaz: Okay, so can you tell us the location of the boost_program_options, boost_serialization, etc. libs?

16:09 < uzipaz> zoq: I don't know, I have no idea, where do I look for those? sry for being an idiot

16:12 < zoq> uzipaz: Maybe it's 'C:/usr/lib/x64/boost/' not sure, you could search for libboost_serialization-vc140-mt-1_60.lib or libboost_serialization-*

16:15 < uzipaz> zoq: when I compiled boost, I manually specifed the path by using "PREFIX=mypath", right now its C:\BoostLibrary\lib

16:16 < uzipaz> zoq: I have libboost_serialization-mgw49-mt-1_60.a and libboost_serialization-mgw49-mt-d-1_60.a in this directory

16:20 < zoq> uzipaz: okay, perfect, so can you take at: https://gist.github.com/zoq/b47f7f33aa0ae1520c9dbfce57e3c2bb and modify the necessary paths accordingly?

16:22 < zoq> uzipaz: I guess, if cmake only has problems to find boost it's sufficient to specify the boost path

16:23 < zoq> uzipaz: "cmake -G "Visual Studio 14 2015 Win64" -DBOOST_INCLUDEDIR:PATH="C:\projects\mlpack\boost.1.60.0.0\lib\native\include" -DBOOST_LIBRARYDIR:PATH="C:\projects\mlpack\boost_libs" .."

16:24 < zoq> uzipaz: can you run (powershell or cmd should work) that command from inside your mlpack build directory?

16:27 < uzipaz> zoq: I am using windows command prompt... I ran cmake .. -DBOOST_INCLUDEDIR:PATH="C:\BoostLibrary\include\boost-1_60\boost" -DBOOST_LIBRARYDIR:PATH="C:\BoostLibrary\lib" -DDEBUG=OFF -DPROFILE=OFF -G "MSYS Makefiles" and I am getting the same error

16:30 < zoq> uzipaz: can't find boost?

16:30 < uzipaz> zoq: yes

16:31 < zoq> uzipaz: Does C:\BoostLibrary\include\boost-1_60\boost contain another folder named boost?

16:32 < zoq> uzipaz: If not use C:\BoostLibrary\include

16:32 < uzipaz> zoq: you can take a look the full error here http://pastebin.com/YSpvAt5d

16:34 < uzipaz> zoq: ok ok.... replacing C:\BoostLibrary\include\boost-1_60\boost with C:\BoostLibrary\include for include path worked

16:34 < zoq> uzipaz: great

16:34 < uzipaz> zoq: I am dumbfounded :D

16:36 < uzipaz> zoq: one last thing that bothers me... that OpenMP is not found... I thought the OpenMP library is included with GCC compilers

16:40 < zoq> uzipaz: It's because the cmake module searches for "boost/boost_header_files.h"

16:40 < zoq> uzipaz: Maybe you have to install a special mingw openmp gcc version? You could also use the one that comes with ms visual studio.

16:41 < uzipaz> zoq: thank you for the help once again and sry if im being stubborn to use mingw, i didnt want all my effort of building everything from source go to waste

16:42 < uzipaz> zoq: im building mlpack right now, lots of unused parameters warnings

16:44 < zoq> uzipaz: no problem, I can't tell you much about mingw and openmp, maybe there is a special version, not sure. It would be great if you tell us in a couple of minutes everything works using mingw :)

16:44 < uzipaz> zoq: with pleasure :)

16:45 < zoq> uzipaz: Warnings about unused parameters in mlpack or boost/armadillo?

16:46 < uzipaz> zoq: I think they are generated from boost

16:47 < uzipaz> zoq: but one of them from mlpack, d:/programming/mlpack/src/mlpack/methods/det/dtree.cpp: In member function 'void mlpack::det::DTree::WriteTree(FILE*, size_t) const': d:/programming/mlpack/src/mlpack/methods/det/dtree.cpp:617:55: warning: unknown conversion type character 'z' in format [-Wformat=] fprintf(fp, "Var. %zu > %lg", splitDim, splitValue);

16:49 < uzipaz> zoq: but I've ran into linking errors at 25% Linking CXX executable ../../../../mlpack_adaboost.exe

16:52 < zoq> uzipaz: can you post the output?

16:57 < uzipaz> zoq: here.. http://pastebin.com/cCfAZfkQ

17:01 < zoq> uzipaz: hm, have you build boost multiple times using different versions?

17:02 < uzipaz> zoq: I am pretty sure just once

17:04 < zoq> uzipaz: can you post the output of 'make clean && VERBOSE=1 make'

17:05 < uzipaz> zoq: VERBOSE is not a recognized command in my command prompt

17:06 < zoq> uzipaz: make VERBOSE=1 ?

17:19 < uzipaz> zoq: http://pastebin.com/FAFsKrPU

17:27 < zoq> I'm almost sure, you build boost with another compiler or different options as you use for mlpack.

17:30 < zoq> uzipaz: Did you build boost manually?

17:36 < rcurtin> I don't understand the pastebin output; it looks like g++.exe is trying to link against libmlpack_adaboost.dll.a ...?

17:37 < rcurtin> -Wl,--out-implib,../../../../libmlpack_adaboost.dll.a

17:37 < rcurtin> but I don't see any linker commands for the other dependencies of mlpack

17:37 < rcurtin> and I don't know what libmlpack_adaboost.dll.a is, or why it's being built; on linux there is no library created for each executable

17:37 < rcurtin> so I am not sure, my experience with mlpack on Windows is not too extensive :(

18:25 < uzipaz> zoq: I download boost 1.60 from http://www.boost.org/users/history/version_1_60_0.html and then followed installation instruction here https://andres.jaimes.net/718/how-to-install-the-c-boost-libraries-on-windows/

19:17 < zoq> uzipaz: hm, I'm not sure if this works, but could you build boost with static libs? "b2 install --prefix=c:/installation/path toolset=gcc --build-type=complete"

23:48 < tham> To make the installer work, I think it would be better if we could make the absolute path to dependence path

23:49 < tham> rather than c:/libs/armadillo

23:50 < tham> make it as ${CMAKE_CURRENT_BUILD}../3rdLibs/armadillo

23:51 < tham> We need some way to find out the link of the prebuild lib, or make sure the link will never change

23:57 < tham> I am willing to contribute the installer, update cmake and write the steps of installation

23:57 < tham> Besides, uzipaz

23:58 < tham> My blog has mentioned how to setup the path of boost in CMakeLists.txt