04-09-2018 08:01 AM
When adding projects to a workspace in SDK, the standard behavior is that the project is linked (i.e. the files are not copied into the workspace but edited at the location they are). XSCT seems to always copy the files into the workspace when running the command "importprojects". Unfortunately this is not what I need (and as far as I know not the common usecase anyway).
How can I import projects into a workspace without copying them in XSCT?
04-09-2018 10:38 PM
With the existing XSCT commands, it will copy the project into the workspace while importing the projects, unlike the GUI option.
04-09-2018 10:51 PM
Yes, this is absolutely clear to me (as I wrote in my post). The point is that this is not the common use-case. Usually the project sources shall be modified in place (i.e. linked project, not copied projects). Are there any plans to implement this?
Unfortunately the .mss file of a BSP must be checked in into version control systems for the project to build correctly. Whenever I change the bitstream, the .mss is modified during the update_hw/generate_bsp/build flow I execute from scripts. XSCT operates on copies of the project, the version controlled .mss file is not changed and the next build will fail.
Of course I can just manually copy the changed .mss back to the original project as workaround. But an option "-link" or "-donotcopy" or something like that should be added to the XSCT importprojects command. As far as I know that is the most common use-case, so XSCT should support it.
04-09-2018 11:05 PM
Yes, I understand your requirement.
We are checking your requirement and will update you once I hear from the concerned team.
09-26-2018 07:34 PM
I would really like to see this import without copy option added to xsct also. Any update?