In Gradle-based projects, the .iml files aren't intended to be checked into source control. The Gradle build files are the source of truth.
On Tue, Apr 1, 2014 at 4:53 AM, Hassan Ibraheem <[email protected]>wrote: > Hi, > > I'm using Android Studio 0.5.3, and pushing the .iml to version control. > > Files are created on Linux ( Fedora ), when created, the .iml contains the > usual: > <module external.linked.project.path="$MODULE_DIR$" .... > > When project is pulled to a different machine ( runs Windows ), after the > gradle sync is complete, the .iml is changed into: > <module external.linked.project.path="C:\Users\UserName\... > > This is the only thing that's changed, all following references to > $MODULE_DIR$ remain unchanged. > > This project has 3 modules, and the 3 .iml files are affected. > > Any idea how to fix this? or work around it? Removing .iml files would > make importing the project into Android Studio a hassle I think. > > Regards, > Hassan > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
