BVLC/caffe "windows environment compiles & examples run"

[briansune]

** Issue summary**
BVLC/caffe "windows environment compiles & examples run"

After successfully compiler and install the caffe in windows environment i.e. (Windows 7 64bit), the build files and folder lead to example run files linking issues.
The latest version of Caffe in BVLC/caffe or windows build complete will generate build folder with “build\ “different files” ”.

** Steps to reproduce & Solutions**
Issues (1) running examples in Root\caffe\examples:
In example MNIST:
By running in Git CMD:
cd $CAFFE_ROOT
./data/mnist/get_mnist.sh
./examples/mnist/create_mnist.sh

First command: “./data/mnist/get_mnist.sh“, should run without problems.
Second command end up with an error that pointing to not “convert_mnist_data.bin” file <- this error is due to Linux environment file linkage, while Windows environment would compile “convert_mnist_data.exe” under examples\mnist\Release folder.

The shell code have two major problems:
@ line 17 to 20: the original code is “$BUILD/convert_mnist_data.bin”
It should be “$BUILD/Release/convert_mnist_data.exe”

After modifying the shell code the “./examples/mnist/create_mnist.sh” should run without error.

Besides the initialization of MNIST:
Training and Testing the Model also follows the same issues.
cd $CAFFE_ROOT
./examples/mnist/train_lenet.sh

After running the shell code in “train_lenet.sh”, the error is asking for a correct folder @ line 4.

The original code:
./build/tools/caffe train --solver=examples/mnist/lenet_solver.prototxt $@

Should modified as:
./build/tools/Release/caffe.exe train --solver=examples/mnist/lenet_solver.prototxt $@

Under the above errors, it is clearly that the build/ install folders are not consistence with the Windows environment.

All example runs or further caffe network runs are problematic due to file linkage issues.

---

Modification in most shell files in "caffe\examples.." or "caffe\build.." are needed, while most shell files are missing critical exe files link.

System configuration
Operating system: Windows 7 64bit
Compiler: VS2015
CUDA version 8.0
CUDNN version 5.1 @CUDA8.0

[LaurentBerger]

@briansune Can you use absolute path in all prototxt files?

[briansune]

@LaurentBerger the solutions are posted, but it is not the best way to solve the problem.
The problem aren't the prototxt files, which are the link in the shell files and the compiled folder arrangements.
The best solution is modifing the generated file link and folder link at the beginning of the make script.
However, modification in the original clone caffe is waiting.