Bug 3629 - mtouch should detect filesystems without working symlink support and fall back to copying
Summary: mtouch should detect filesystems without working symlink support and fall bac...
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2012-02-24 04:14 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-02-24 14:06 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2012-02-24 04:14:34 UTC
It appears that simulator builds don't work correctly on certain filesystems such as Parallels shared drives. This is probably due to issues with symlinks on those filesystems.

mtouch should detect filesystems without symlink support (or with broken symlink support) and fall back to copying. This would fix the problem, though at the expense of a longer build time.
Comment 1 Sebastien Pouliot 2012-02-24 09:54:18 UTC
I'll setup to duplicate this.

In the meantime it's possible to use --nofastsim (or the linker) to workaround this (at the extra expense of rebuilding a launcher each time).
Comment 2 Sebastien Pouliot 2012-02-24 14:06:50 UTC
fixed in master
318c1cb8c99a464369e2f8468696a9b0d78c91cd