When I point an slnfile at a single project with one build spec, four different project items are generated, but only one of them carries the proper dependencies.
The four different project items are in the attached screenshots. Only the second item seems to be "right", or at least this is the item that I was expecting when I started debugging.
Due to how the ordering map is generated in SubGenerateListToOrder.vi, the dependencies of the "right" project item were added to the map for the purpose of build ordering, but the dependencies are left out of the project item that is actually built, which results in the libraries not being swapped.
Extra code can be added to the in place element structure of SubGenerateListToOrder.vi to add dependencies to any map elements that are being modified to ensure the full list is maintained (I have tested this method and confirmed its validity), but is this the right way to approach this issue?
When I point an slnfile at a single project with one build spec, four different project items are generated, but only one of them carries the proper dependencies.
The four different project items are in the attached screenshots. Only the second item seems to be "right", or at least this is the item that I was expecting when I started debugging.
Due to how the ordering map is generated in SubGenerateListToOrder.vi, the dependencies of the "right" project item were added to the map for the purpose of build ordering, but the dependencies are left out of the project item that is actually built, which results in the libraries not being swapped.
Extra code can be added to the in place element structure of SubGenerateListToOrder.vi to add dependencies to any map elements that are being modified to ensure the full list is maintained (I have tested this method and confirmed its validity), but is this the right way to approach this issue?