I am learning my way through the vast Haxe ecosystem. While this community forum does not seem to have many discrete categories of topics, it seems like the preferred place to get assistance with this topic. [Earlier today I posted a closely-related request for help with the community.openfl.org forum, and received excellent assistance, and I know there is wide-spread cross-pollination between the various Haxe sites/groups, but the closer I get to some understanding of the component pieces, the more it seems like I should really find a way of communicating directly with the folks responsible for HXCPP. Other than hijacking some existing topics and/or closed bug issues, opening a new topic here appears the best choice.]
So, with a suggestion from Joshua Granick, I got the clue that googling for HXCPP_COMPILE_CACHE might be useful, and indeed, that opens some links to material discussed in the nice SnowKit/HXCPP_Guide. Following that path gets me to the /haxetoolkit/haxe/lib/hxcpp/3,4,188/docs/build_xml path where there is a welter of .md files. And over at the github site https://github.com/HaxeFoundation/hxcpp/issues/666, there is some helpful material, but I am not adept enough with any of the tools in the toolkit to be able to answer my own question, which is basically this:
Shouldn’t it be possible to share a single installation of VisualStudio 2017 on a windows workstation that dual boots between Windows 7 and windows 10?
It took me 4 hours to get through the install of the Community Edition under Windows 7 and I would not only like to avoid all that time, but all those gigabytes of space if I could just have Haxe installed/running on the Windows 10 boot pointing to the location of the necessary SDKs.
If, as it seems might be the case, the only real dependency/connections between the HaxeLib world and the MS CPP libraries is a couple of paths to where the VS stuff resides in my file system – nothing in any registry settings, nothing other than the convenience of some Shortcuts here and there – can someone provide a simple example of how to modify the .bat files with hard-coded paths that will allow haxelib and/or lime and/or openfl to successfully build for a windows target?
I have the feeling that there are quite a few other users or wannabe users of these powerful tools for development of desktop applications caught between the 32-bit world of Windows 7 and the 64-bit world of Windows 10. If the documentation and a couple of hacked .bat files would do the trick, I would be very, very appreciative.