oceanclub wrote:So you need to include these files from your child project in source control - they're required to build your output.
Sorry but I don't get the if-then in this case. Once I kick off the build of the child project, it copies the files it needs from the relevant global project, as specified in the global.flimpfl file. (The "Auto Sync Import" dialog that pops up.) Those files are assumed to be already on the user's machine, but in the Global project, not in the child project.,
What I mean is that Flare requires these files from your global project to build your project. If they're not in source control, then you add a dependency (to use an import with auto sync).
I don't use "Auto sync" in my target, as I need to control when newer imported files are introduced in a project. This means I must include these imported files in source control.
But more importantly, it also means that if I get the project on different PCs, I know the project will be exactly the same on each PC, and will build the same output.
If didn't include imported files in source control and relied on "Auto Sync", then it introduces a few things that I wouldn't be so happy about:
1) It assumes that on each PC, the person has set up the global project in the correct location, otherwise the import will not work.
2) It assumes that on each PC, the local version of the global project is always kept up to date; i.e. the person must ensure they do a "get latest" on the global project, before running a build in the project that imports from that global project. (You can mitigate this by putting the global project in a network folder, rather than a local folder).
3) There's a possibility that the project will not be the same on everyone's PC, as certain files/folders are not in source control.
4) If a user modified an imported file, would it be overwritten by the auto sync import? I know the manual import does not automatically overwrite local project files that are newer than the global project (marked in red), and these usually require investigation as it could mean that the imported files have accidentally been modified. At least when the imported files are in source control, you can't have file variations between one PC and another.