FPGA compilation results needed in source code control

[D*]

The FPGA compilation results should be copied to a file in the folder with the bitfile.  This is needed to track the history of compilation results, especially useful when using source code control.  Right now they get overwritten with each recompile.

Adding a Post-build action VI to the FPGA build spec, would also enable something like this.

[CMal]

The FPGA Idea Exchange would probably be a better place for this.

[Darin.K]

And if you are lucky, both people who follow that board will Kudo it.... 

[D*]

I initially thought that, but then saw what Darin observed.  but I'll give it a try..... go here to kudo:  Reposted in FGPA Idea Exchange

[CMal]

Here is a link that works.

Here's why I think it is better to post ideas like this on the product-specific idea exchanges.  Out of all the people who visit the generic LabVIEW Idea Excange, only a small portion of them are FPGA users, so even the best FPGA-specific ideas are only going to get a small number of votes compared to other good ideas that appeal to a wider audience.  When you post the idea on the FPGA exchange, it has a better chance of standing out against other FPGA ideas.  It might not get as much visibility, but it also won't get drowned out in the noise.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined. 

[RavensFan]

The correct link to get to the idea in the FPGA exchange.

http://forums.ni.com/t5/LabVIEW-FPGA-Idea-Exchange/FPGA-compilation-results-log-needed-especially-fo...