On Mon, Jul 25, 2022 at 9:24 AM Bin Meng <
bmeng.cn@gmail.com> wrote:
>
> On Wed, Jul 20, 2022 at 12:12 AM Bin Meng <
bmeng.cn@gmail.com> wrote:
> >
> > From: Bin Meng <
bin.meng@windriver.com>
> >
> > At present winsymlinks is set to 'nativestrict', and its behavior is:
> >
> > a) if native symlinks are enabled and <target> exists, creates
> > <destination> as a native Windows symlink;
> > b) else if native symlinks are not enabled or if <target> does
> > not exist, 'ln -s' fails.
> >
> > This causes the following error message was seen during the configure:
> >
> > "ln: failed to create symbolic link
> > 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory"
> >
> > Change winsymlinks to 'native' whose behavior is most similar to the
> > behavior of 'ln -s' on *nix, that is:
> >
> > a) if native symlinks are enabled, and whether <target> exists
> > or not, creates <destination> as a native Windows symlink;
> > b) else if native symlinks are not enabled, and whether <target>
> > exists or not, 'ln -s' creates as a Windows shortcut file.
> >
> > Signed-off-by: Bin Meng <
bin.meng@windriver.com>
> > ---
> >
> > .cirrus.yml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> Ping?
Reviewed-by: Yonggang Luo <
luoyonggang@gmail.com>
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo