On 8/31/2010 8:19 AM, David Comley wrote:
--- On Mon, 8/30/10, Keith<keithvz at verizon.net> wrote:
I've worked both with Ubuntu 9/10 and Windows XP/Vista/7
which both work fine with ISE and programming tools.
Keith, have you had any issues when transferring projects between the two environments ?
I'm about to start working on a project that was originally developed using the
Windows version of ISE, but will be maintained using the Linux version of ISE under SuSE
11.
-Dave
While that's not my normal M.O., I did once go Windows -------> Linux
without problems.
The only related issue that I've run into involves naming projects,
directories that store projects, etc. Some of the utilities that ISE
calls (still?) do not handle spaces in the filename string. Some
notable problems with Windows might be "My Documents" or "Program
Files." This can also be a problem with Linux because they don't call
the executables properly (ie with quotes for arguments, or whatever)
I've also seen filename LENGTH problems.
These problems show up multiple places, not the least of which, in the
EDK for MicroBlaze, their 32-bit softcore processor.
The error messages that result are not always file-not-found errors ----
you get cryptic errors that won't directly point you to the root cause.
Oh, and one other thing: Make sure you "cleanup" the project in Windows
ISE before you move things. There are a bunch of intermediate files
that store directory related items that won't be there in the new file
system. Even moving projects from directory to directory within Windows
this problem can show up. It's not a big deal --- just keep an eye out
for it. Once again, the error messages you get will not easily point
right at this being an issue. The main thing is that if you instantiate
a module, and that module is in the project, but can't be found when
synthesizing, then you need to cleanup and rebuild. If you are familiar
with the icons in the project navigator, the modules not having the
correct icon next to them will usually indicate that this needs to be done.
In general, if you synthesize and get weirdo errors related to "no such
module", then cleanup and rebuild. It almost always fixes the problems.
Keith