Regenerating msvc-setup.bat

What logic in jam files or Boost Build causes an msvc-setup.bat script 
to be regenerated ?

I have been trying to test with Intel C++ on Windows and the Boost Build 
intel-win.jam file. I noticed that intel-win.jam appears to use a single 
msvc-setup.bat script in the 'boost\bin.v2\standalone\msvc\intel' 
directory of my output for all versions of Intel C++ on Windows and for 
all choices of VC++ compatibility on any version. Thinking that can not 
be right I tried deleting my output's 
'boost\bin.v2\standalone\msvc\intel\msvc-setup.bat' file to see what 
would be regenerated but now the file ends up completely empty each 
time, which of course causes vc++ compatibility to fail when testing a 
Boost library with any version of Intel C++ on Windows. Oops ! I can not 
make out in the intel-win.jam file any clues of how to get the file 
regenerated with the correct environment variables for whatever VC++ 
compatibility the Intel C++ for Windows toolset I am testing actually 
has. Moreover I am pretty sure that having a single msvc-setup.bat for 
all versions of Intel C++ on Windows and vc++ compatibility for any 
given version can not be correct design, and would like to correct this 
so that each Intel C++ version and vc++ compatibility has its own 
msvc-setup.bat generated in different subdirectories of output's 
'boost\bin.v2\standalone\msvc\intel'. And yes I am using the wonderfui 
Boost Build debugger to step through intel-win.jam code but I can not 
see where all this logic is happening to generate/regenerate 
msvc-setup.bat files even as I am pretty sure it is through some rules 
in msvc.jam itself. Any help or clues would be greatly appreciated.

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build