aaronmarkham commented on a change in pull request #12962: fix broken links and reorganize build from source page URL: https://github.com/apache/incubator-mxnet/pull/12962#discussion_r228629720
########## File path: docs/install/build_from_source.md ########## @@ -183,53 +199,88 @@ nosetests --verbose tests/python/gpu/test_nccl.py **Recommendation to get the best performance out of NCCL:** It is recommended to set environment variable NCCL_LAUNCH_MODE to PARALLEL when using NCCL version 2.1 or newer. +<hr> + +### Build MXNet with C++ -### Build MXNet with Language Packages * To enable C++ package, just add `USE_CPP_PACKAGE=1` when you run `make` or `cmake`. +<hr> ### Usage Examples -* `-j` runs multiple jobs against multi-core CPUs. Example using all cores on Linux: + +* `-j` runs multiple jobs against multi-core CPUs. + +For example, you can specify using all cores on Linux as follows: ```bash -make -j$(nproc) +cmake -j$(nproc) ``` -* Build without using OpenCV: + +#### Recommended for Systems with NVIDIA GPUs and Intel CPUs +* Build MXNet with `cmake` and install with MKL DNN, GPU, and OpenCV support: ```bash -make USE_OPENCV=0 +cmake -j USE_CUDA=1 USE_CUDA_PATH=/usr/local/cuda USE_CUDNN=1 USE_MKLDNN=1 Review comment: It's interesting that we tend to promote using MKLDNN for better performance and in the CMAKE instructions, they imply that it is turned on by default. However the config.mk has it turned off. I thought it was supplied as a submodule and it is on by default. Is the config.mk out of date? And yes, it should be mentioned what happens when you just run `make`. Seems like right now you get: opencv, openmp (that doesn't work on mac out the box), atlas || apple Looking this config.mk file actually makes things even more unclear... @anirudhacharya Can you propose the logic that is followed and the recommended flags per general situation? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
