I apologize for a newbie question; actually I even have to apologize for posting to this forum. I have diligently searched all the impressive sites dealing with the Haxe community of tools and cannot find an answer to the question of why recompilation of cpp sources seems to be necessary. I sort of suppose this is a lime question, but maybe it is an HXCPP question. It is, however, in attempting to target windows in the way suggested by OpenFl that the matter most clearly comes into view, so this is where I will try to get the answer.
Whether using the HaxeDevelop IDE, or just command line execution, it seems that if I target windows, I will see a long, long list of cpp files being compiled. OK, fair enough, the documentation does alert me to the fact that that will occur, but the surprise is that it will occur over and over again if I just try to compile the same HelloWorld example in two separate projects. Or, as my experimentation has taught me, I can induce the same result if I use the Clean Project feature inside a single project in HaxeDevelop.
In other words, it seems to me, the toolchain has no concept of libraries of pre-compiled code which only needs to be linked to specific application instances. This is so fundamental, and clearly the folks who have put man-centuries into the amazing cross-platform capabilities of the Haxe ecosystem must know all of this in their very bones, so I must imagine that I have simply not found whatever switch one is supposed to set to tell the build process to save the object files into some convenient library hierarchy rather than compiling the same code for every source project by which it may be used. Or, is there a build library step that I have not stumbled upon?