> At 06:58 AM 4/13/2006, Ken - N9VV wrote: [snip] > 2) Because of #1, I would assume that the "official" release of PowerSDR > will always be built on the MS toolchain (guaranteed compatibility). So, > your alternate toolchain has to be able to either use all of MS's files or > smoothly convert back and forth. >
Whatever else happens, and why, this is sheer FUD. Back when the world was a little less complex, I used Borland and MS C++ IDEs regularly. Never noticed any serious difference. As long as they all link to the same underlying APIs, DLLs, Libraries, there's no reason to fear a non MS tool chain _as such_. The headache seems to be that MS (and now everyone else) seems to be creating their own superstructure based on anything but makefiles. I've never been a fan of "make" but at least it provided a common "language" for all this kind of stuff. Dual maintenance of all that could be an issue. We can't have many alternatives. All the cruft of Makefiles, et. al. is all deadweight time that generates no bug fixes and no features. So, six versions are clearly out. But, whatever choices Gerald makes over time, this is not, IME, a serious consideration. As long as the toolchain can find the DLLs et. al., we're fine. If MS' environment is more productive or something, or Flex doesn't want to even try to migrate, that's a different kettle of fish. But, from its infancy to now, non MS stuff has peresisted and there's no reason to expect otherwise. Larry WO0Z PS, I and many others run on the betas at least as much as the general release anyway. My bet is on Flex' testing, not on MS compilation as such anyway.
