I got an old version of ISE to run okay under a relatively recent version of WINE. Xilinx is not hostile to WINE. If you can't get ISE to run under WINE, you may be able to help both from the WINE community and from Xilinx to get them to fix the problems, although I can't say how long that would take. It would be beneficial for all of us to be able to get that to work in the long run.
On 5/20/05, Jack Carroll <[EMAIL PROTECTED]> wrote: > On Thu, May 19, 2005 at 03:17:53PM -0700, Eric Smith wrote: > > > > In practical terms, for something as complex as an FPGA tool chain, > > it is possible that we may be better off with the free-as-in-beer tools > > anyhow, since they are fully supported by the vendor. > > There's also the point that the tool chain is useless without the > target chip, which is a proprietary product anyway, and probably always will > be. In this situation, I'm willing to depart from my strong bias toward > open-source everything. If FPGAs became multi-sourced items, there'd be > more of a reason to try for at least a minimally capable complete open > source tool chain, to insure longevity. > > Let me try to get a grasp of another point. Someone said the Xilinx > Webpack runs under WINE. Has that been tried? If so, it gives me a reason > to get familiar with WINE; so far I haven't attempted to use any > MS-compatible applications here. Also, does that tool chain target the > specific FPGA the project has selected? I'm not clear on that. > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
