Closed Jookia closed 11 years ago
mhh, copy is doing implicit more than copy_file. If we want to make sure to copy a file, we should use copy_file. If we don't care about what type of "file" it is (symlink, file, directory), we can use copy
Copy runs copy_file if it's a file. We could add a path type check if needed. I don't know of another way around it, but my fix shows that there's some weird linker stuff going on.
yes, I don't think we should "change behavior" here, but fix the linker issue directly. We could add Boost_FILESYSTEM_LIBRARY to the usercore and mcfcore library list, but I won't do that, because we don't use this interface there directly, but via another (static) dependency like util and util_fs. That's why I want to know where this linking error is comming from. But maybe we should move all of this static libs to shared libs aynway (to reduce time needed to find the cause of such errors and to reduce binary size)
I think we should not allow it to copy directories in a function name copyFile.
@Jookia how do you like this fix #542? It will pretend the same error with other methods using scoped enums in boost (copy_file is currently the only one, but you knows which guy wants to use one of these methods and wondering about a stupid linking error)
That's a great fix.
So I am closing this request
This fixed #533. For real.