Xilinx IPCores losing configuration: Absolute path problem?

[Intaris]

We are using LabVIEW FPGA 2015.

We utilise quite a few Xilinx IPCores (Multiply adder and so on) but I keep running into problems.  After committing changes (and checking out to a different directory on disk), I am often met with the IPCores claiming that their configuration has changed since they were last loaded and when I enter the wizard, the settings are back to default.....  The xco files and such are there, I can verify this.  Is it a problem that we don't commit the sim folder?  Could this be part of the problem?

Does anyone else have experience with this?

[Intaris]

I've done some more digging:

All information regards ISE 14.7 in LabVIEW FPGA 2015. We're using a Virtex 5 target.

The Xilinx IPCore dialog requires an absolute path for configuration.  However, if I copy my repository to a new disk location and open up the project there, go the IPCore configuration and have a look, the NEW path is there, so somebody somewhere is updating the absolute path.

If, however, I delete the VHD, DLL, XCO files from this location when LV is closed, the OLD absolute path re-appears.  This is kind of worrying for me because the old path may well be valid.  If I then modify the Xilinx IPCore and later commit the local files (in the NEW, not the OLD path) then I'm not committing the changes.  LabVIEW / Xilinx does this re-mapping without telling me anything whatsoever.

Is there a way to get this behaviour under control? I would at least expect to be given a warning that things expected at path NEW were instead loaded from path OLD.  Better still would be not automatically searching and taking the first file that meets the filename criterium.  This is something which has be a bit worried.

OTOH, we're thinking of moving to a different FPGA target which would require VIvado and most likely a move to 2018.  Is this kind of behaviour different in Vivado? If it is better, this will be added to the list of annoying things which may be better after upgrading.

[DesasterMaster]

Were you able to test it with LabVIEW 2018 and Vivado Software?

Is the behaviour still the same?

I'm not sure if this is a LabVIEW or an Xilinx Issue.

[Intaris]

I haven't been working with Vivado yet, that's something we'll likely be doing some time soon (this year), also a switch to LV 2018.

It seems there is a hodge-podge of LabVIEW and Xilinx path magic going on with the dialog for launching the IPCore wizard (Everything within the wizard is Xilinx, but the path passed to it is almost certainly a LabVIEW thing, and here LabVIEW does some auto-conversion of paths as outlined above.

We have stability at the moment. We know it can be a problem and try to keep an eye on the situation.  The DLLs listed as dependencies actually help to root this problem out.  We can see if there are any files listed outside of our actual current repository.

Things seem to be working at the moment.