Generated op.h cannot be compiled

I am trying to build MXNet (getting latest from git) from source on Windows 10 (Visual Studio 2017).
I’ve followed steps mentioned here: http: //mxnet.incubator.apache.org/versions/master/install/windows_setup.html

***** ISSUE: When built from source, the op.h file generated cannot be compiled as lrs, wds parameters in the file doesn’t have any data type. *****

e.g.
inline Symbol multi_sgd_update(const std::string& symbol_name,
const std::vector& data,
lrs,
wds,
mx_float rescale_grad = 1,
mx_float clip_gradient = -1,
int num_weights = 1) {
return Operator(“multi_sgd_update”)
.SetParam(“lrs”, lrs)
.SetParam(“wds”, wds)
.SetParam(“rescale_grad”, rescale_grad)
.SetParam(“clip_gradient”, clip_gradient)
.SetParam(“num_weights”, num_weights)
(data)
.CreateSymbol(symbol_name);
}

This is case for all the lrs and wds parameters.

Just for more info, here is cmake file.
Details:

Compiler: Visual Studio 2017 (15.9.7)

Environment info

----------Python Info----------
(‘Version :’, ‘2.7.10’)
(‘Compiler :’, ‘MSC v.1500 64 bit (AMD64)’)
(‘Build :’, (‘default’, ‘May 23 2015 09:44:00’))
(‘Arch :’, (‘64bit’, ‘WindowsPE’))
------------Pip Info-----------
(‘Version :’, ‘7.0.1’)
(‘Directory :’, ‘C:\Python27\lib\site-packages\pip’)
----------MXNet Info-----------
No MXNet installed.
----------System Info----------
(‘Platform :’, ‘Windows-8-6.2.9200’)
(‘system :’, ‘Windows’)
(‘node :’, ‘BLRW-SGH419QXT8’)
(‘release :’, ‘8’)
(‘version :’, ‘6.2.9200’)
----------Hardware Info----------
(‘machine :’, ‘AMD64’)
(‘processor :’, ‘Intel64 Family 6 Model 58 Stepping 9, GenuineIntel’)
Name
Intel® Core™ i7-3770 CPU @ 3.40GHz

@lebeg @gavin can someone in the build team familiar with Windows build can help? Thanks!

Can someone please help? Is it not recommended to compile MXNet on Windows? I’ve tried almost everything what I can thinking of, with or without cuda, OpenBLAS vs Inetl mklml but I am not able to generate CPP Package! I’ve been trying this from two weeks, have updated from Windows 7 to 10 hopeing to solve the issue.

It seems an open issue currently (#14116), as in