Yeah, google-fu fails when you are the first to try something -- or when those who have gone before are too foolish to ask their question in public!
This way you get to both pose the question and the answer for the next person to try this. Anyway, the first thing I'd do is to think long and hard about my reasons for wanting to do this. If there's really not enough benefit, then don't do it; that's the simplest way. Otherwise, I'd write an ant script, and add an ant builder to my project that copies it in from the source. You'll want to set it up to run whenever the source changes, and to refresh the output file whenever the script runs. This way, it'll run the script, do the copy, and then tell Eclipse that the file has changed. But you won't be able to edit the file in res/ in Eclipse, without losing your changes. That may be a steep price to pay. A better solution, in my opinion, is to have them be separate files with a common ancestor, and use your revision control systems merging capabilities to merge changes back and forth. For example, with Subversion, use 'svn copy source/layout/main.xml res/layout/main.xml' to make the local res/layout copy, such that it is a descendant of the source/layout file. Then use 'svn merge' to merge changes between the two files. (Of course, you'll need 'svn commit' after each step, before touching these files again, but you can combine that with other changes). A big advantage of this approach is that you can have changes which you do NOT merge back, but only exist in one of the projects using the common source. And yet you can continue to merge other changes back and forth as needed. It's not as automatic, but it also leaves a better audit trail. On Feb 22, 6:47 am, Adrian Vintu <[email protected]> wrote: > Ok, I found it. Seems the resources are built using the aapt.exe command > line. This means, only physical files are taken into account... > > Anyone has an idea on a workarround for this? - to also make the linked > files be physically included in the RES folder but also be updated if the > source changes? Without using symlinks and stuff like that? > > Thank you, > BR, > Adrian Vintu > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
