On May 23, 5:07*am, LittleAlex <alex.lo...@email.com> wrote:
> I have been successful converting a project from GUI to command line
> with identical bit files.

Hi LittleAlex, thank you for your comments.

We too get identical bitfiles (excluding header), but my concern is
that the intermediate files are all different. All this does is give
me confidence that *this* build is identical, but who can say if
future builds will be? We have no way to test this for every build
either. For serious use of the Xilinx tools in an engineering
environment, this sort of behaviour is ridiculous.

> Take a very close look at the log files left behind by the GUI build.
> There are options that you will probably not recognize - the GUI knows
> better than you what you want it to do

In fact the GUI got it wrong - it said to use the -i flag, but in fact
this was wrong and what was required was removal of the -i flag, and
use of the -uc flag instead.

> You can get rid of the -intstyle ISE flag. *I use a .prj file format
> and that works just fine for me.

What flow do you use with that? -intstyle xflow?

> Most options can be set in a number of places. *I'm not 100% sure
> which location for the option has priority; I had some weird results
> which went away when I made them all match.

Is the .prj format similar to Synplify's TCL .prj format? I'll have to
look up the .prj format - could be useful.

> Another thing to look out for: *The GUI scatters work directories all
> over the place. *Weirdness in these directories can cause run to run
> inconsistencies; audit the location and cleanup of these directories
> carefully.

Yes, our Makefile cleans up pretty well. A 'git clean -fdx' also does
the trick during a build.

Regards,

-- David.