But at least for now gcc48 can be used and this should work nicely with "make". I'm wondering because as far as I understand the apple strategy, gcc will be superseeded by clang in the long run. > Can the FFS make file construct be reused? Unlike wxWidgets boost is updated frequently, so I expect this to work. FFS heavily relies on boost::thread, which is one of the boost components that get the most fixes with each release, so I'll try to be as current as possible. With regards to boost though I'll try to compile manually.
If they work, then this would be a convenient solution. I'll test both boost and wxWidgets macport versions. Compiling wxWidgets manually produces all kinds of crazy error: compiling fails with not finding "wcsncasecmp" even though, the configure-step before found it explicitly. > We can get wxWidgets from macports too: Also added "hash gcc" - no idea what that does, but gcc48 is selected and working now. I found as a workaround "sudo port clean -all all", then installing gcc48 again, followed with "sudo port select gcc mp-gcc48" did the trick.
FREEFILESYNC MAC HOW TO AUTOMATE INSTALL
"sudo port install gcc48" failed with some error mentioning some "ld64"-related file already existing. I've installed macports, but it didn't go too smooth: My Mac environment is x86_64 with OS X 10.8.2 and Xcode 4.6. Once the environment is running, the source code changes should be a piece of cake. Since you two seem to have experience on Mac, maybe you can help me to set it up. The showstopper for me right now is that I have no working build environment on Mac. Are you currently working on a mac port, or is it just something you plan to do in the future
0 kommentar(er)
