When you were using it on Windows, were you: (1) Using "mxmlc.bat"/"mxmlc.exe", "mxmlc.jar" directly, or "fcsh"? (2) What terminal were you using? e.g. cmd (Command Prompt), PowerShell, MinGW, Cygwin, GitBash, etc. (3) Were your files hosted on a normal NTFS drive? (4) What version of the Flex SDK? (5) What version of Windows? (6) Using Intel-based hardware?
Sincerely, James M. Greene On Jan 13, 2015 10:58 PM, "WesleyJohnson" < [email protected]> wrote: > James M. Greene wrote > > I've NEVER had incremental builds work on Windows or OSX when using > > `mxmlc` > > directly... always rebuilds. :-\ > > > > Not certain about its success through > > FlashDevelop/FlashBuilder/FlexBuilder/FlashIDE...? > > > > Sincerely, > > James M. Greene > > I got the project setup on a Windows PC and I'm back to having incremental > working just fine. I can call 'mxmlc' over and over again on the same file > and it finds the cache and alerts me that the file doesn't need recompile > and happily continues on. Very odd it works on Windows and not OSX. In my > testing, I did run across some interesting things, however: > > If I change the modified date of any of the referenced files without > changing the contents they will be recompiled with a message stating one of > the files changes. > > If I change the content of a file, then of course I get the 'failed to > match > compile target cache' or whatever that notification says and it will > recompile. > > If I change a containing folders name, I also get the 'compile target > cache' notification and it rebuilds the file. I don't know why the folder > name would matter, I guess because I'm using relative links in my .css file > to reference a parent directory with the embedded assets. > > Another interesting thing is the checksum on the compiled file is different > on OSX and PC. I assume, again, it may have something to do with the > differences in the compiler itself or because the folder structures are > different and I'm using those relative paths in the embeds so the when > those > paths are evaluated in the compilation process it sees they're different. > Not sure. > > Anyway, for what it's worth - it's working on Windows again, but OSX is > still a loss. The key for me to get it going on windows is blanking out the > metadata using '-raw-metadata ""'. I suspect maybe just wiping out the date > using '-date' would be sufficient, but it's working so I'm leaving it. > Hopefully Apache will figure out the OSX issue at some point so incremental > works on there as well. > > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/MXMLC-incremental-not-working-on-OSX-tp9380p9394.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
