Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I had assume I could just do this, but I don’t have a way to check that resource forks went along for the ride.
NSFileManager *fm = [NSFileManager defaultManager];
[fm copyPath:absSourcePath toPath:absDestinationPath handler:err];
edit: I need to copy in a 10.4-6 compatible manner. (Yes, really 10.4.)
Yes, everything gets copied, including file permissions, subdirectories, symbolic links, you name it. The documentation recommends using
copyItemAtPath:toPath:error:in 10.5 and later, so you might want to work that in if possible. It’s not available on 10.4, so you’ll have to usecopyPath:toPath:handler:there.I guess I should note, it may depend on the destination filesystem; I don’t know what would happen if it didn’t support resource forks. I guess it would use Apple Double?