Any ideas why incremental flex compilation would not work for successive compilations of identical source?

Question

I am running mxmlc in the command-line with -incremental=true. Flex is building the cache file using a checksum the first time. Subsequent compilations fail with this message:

Failed to match the compile target with path_to_cache/projectname_329043.cache. The cache file will not be reused.

1. path_to_cache exists
2. the cache file exists in path_to_cache
3. the compiler is not trying to create a new cache file, so I assume it is generating the same checksum

My environment:

1. Flex 3.0
2. Mac - OSX 10.4.x

Answer 1

It could be a permissions issue. Have you tried running with sudo? I wouldn't recommend doing that permanently, but if using sudo makes the error message go away, then you know it's a permissions issue; and you can move on to the proper way to resolve it.

You could also try going into Disk Utility and doing a check/repair of disk permissions. OSX has been notorious for needing this done occasionally.

Answer 2

I just ran across this issue myself and after not finding the answer anywhere on the web, I bashed my head against mxmlc in practically trail-and-error until finding the answer. In my case, I was regenerating the flex config xml file each time I compiled from within ant. It turns out that this is the error you get in the case where it thinks the config has changed. You can test this by simply touching your config file and running against unmodified sources. So, if the timestamp is changing on your flex config.xml between compiles, that is likely the culprit.