The second issue is due to repo being empty. If XSCT is started from the console, a workspace is not set and getws returns empty. The wiki recommends "sw/ws" for a workspace (which has the right gitignore set), which makes the /./src/checkout.tcl form work properly The GUI asks the user for a path, so if XSCT is started from the GUI, it will have a workspace set. Workaround is to use the form, or an absolute path to checkout.tcl.Ĭommand returns the path to workspace set when Vitis was started. " Workspace already exists and needs to be closed first"įixed the first issue, it was due to a bug. If I follow the instructions that I was given here, which says to run the XSCT command from within Vitis. Perhaps you forgot to check out the submodule? Try git submodule update.Īs the error says, the repo directory is empty, but I did checkout the submodules. Repo directory /home/user/source/Genesys-ZU/sw/repo is inexistent or empty. INFO: Running /home/user/source/Genesys-ZU/sw/src/repo/0_sw_repo.tclĬhanging back working dir to: /home/user/source/Genesys-ZU/sw/ws home/user/source/Genesys-ZU/sw/src/3eg_fsbl/145_build_app.tcl home/user/source/Genesys-ZU/sw/src/3eg_master/145_build_app.tcl home/user/source/Genesys-ZU/sw/src/3eg_fsbl/45_standalone_app.tcl home/user/source/Genesys-ZU/sw/src/3eg_master/45_standalone_app.tcl home/user/source/Genesys-ZU/sw/src/3eg_domain_fsbl/25_standalone_bsp.tcl home/user/source/Genesys-ZU/sw/src/3eg_standalone_bsp/25_standalone_bsp.tcl home/user/source/Genesys-ZU/sw/src/3eg_hw_pf/5_hw_pf_xsa.tcl home/user/source/Genesys-ZU/sw/src/repo/0_sw_repo.tcl INFO: Running /home/user/source/Genesys-ZU/sw/ws/./src/checkout.tcl. So I assume that "getws" something that Vitis defines. INFO: Targeting /home/user/source/Genesys-ZU/sw/ws for workspace creation.Ĭhanging back working dir to: /home/user/sourceĮRROR: Self not found while deep searching /home/user/source/Genesys-ZU/sw/srcĬouldn't read file "/./src/checkout.tcl": no such file or directory INFO: Running Genesys-ZU/sw/src/checkout.tcl. Xsct% source Genesys-ZU/sw/src/checkout.tcl When running from above the repo directory. If I run the script as described in the Git workflow listed above, it fails as below. When trying to run the checkout.tcl script, errors occur. This is a public inbox, see mirroring instructionsįor how to clone and mirror all data and code used for this inbox Īs well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).I am having an issue with the Digilent Git workflow. 12:24 Q: warning: unable to rmdir 'submodule': Directory not empty Ulrich WindlĬode repositories for project(s) associated with this public inbox links below jump to the message on this page. Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) submodule directory contains untracked files Įnd of thread, other threads: > submodule directory was "mostly deleted", only leaving two object files that > When I tried "git checkout master -recurse-submodules" instead, the > expected to remove submodule directories manually before switching branches? > Well obviously the directory is not empty. > warning: unable to rmdir 'submodule': Directory not empty > checkout another branch that does not (yet) have that submodule, I get an > When a branch uses a submodule (named "submodule" here), and when you > I wonder whether you'd think this is a bug: > Ulrich Windl schrieb am um 13:24 in Nachricht : Sorry, I should have mentioned: git 2.26.2 on SLES12 SP5 12:24 Q: warning: unable to rmdir 'submodule': Directory not empty Ulrich 12:25 ` Ulrich Windl 0 siblings, 0 replies 2+ messages in thread * Antw: Q: warning: unable to rmdir 'submodule': Directory not empty submodule directory contains untracked files won't delete those." be better? When I tried "git checkout master -recurse-submodules" instead, the submodule directory was "mostly deleted", only leaving two object files that weren't ".gitignore"d. The point is: Is the user expected to remove submodule directories manually before switching branches? Well obviously the directory is not empty. Warning: unable to rmdir 'submodule': Directory not empty When a branch uses a submodule (named "submodule" here), and when you checkout another branch that does not (yet) have that submodule, I get an error message saying: I wonder whether you'd think this is a bug: Q: warning: unable to rmdir 'submodule': Directory not empty mailing list mirror (one of many) help / color / mirror / code / Atom feed * Q: warning: unable to rmdir 'submodule': Directory not empty 12:24 Ulrich WindlĠ siblings, 1 reply 2+ messages in thread
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |