Re: Can we expect ISE Gui and makefile to produce identical bit files?
"David Antliff" <david.antliff@gmail.com> wrote in message
news:b284f6e3-e758-47e7-a392-2e0ce77c73f8@p6g2000pre.googlegroups.com...
On May 27, 3:25 am, "MikeWhy" <boat042-nos...@yahoo.com> wrote:
> I just use the <project>.xise file. Starting the gui with just that file
> in
> the project directory produces all the other files.
Assuming you meant '.ise' not '.xise' (apologies if there really is
a .xise file, I haven't seen one) - as I mentioned earlier, we cannot
use the .ise file as an input to our build system because it
constantly changes. This also means we would prefer not to have it
tracked by our source control tool (git) as a constantly changing file
is nothing short of exceptionally annoying. So if we can generate
an .ise at build-time from a TCL script, we can provide a way to
generate a non-controlled .ise for use locally in the GUI tool. I
still don't want to use the .ise as a build input.
=========
I really did mean explicitly .xise, as opposed to .ise. It's apparently new
with 11.1. It looks like well formed XML, but I didn't look in any detail.
The .ise file looks to be a TCL script, likely generated from .xise.
|