ccMSC / ckb

RGB Driver for Linux and OS X
http://forum.corsair.com/v3/showthread.php?t=133929
GNU General Public License v2.0
1.34k stars 170 forks source link

Problem with mac, el capt 10.11.6 #566

Open scootcam opened 7 years ago

scootcam commented 7 years ago

When i loaded ckb.pro into qt5 and then when i went to build it, it said that a "carbon" thing wasnt working

JarrenJ commented 7 years ago

same, lol i just opened an issue about it last night :P

scootcam commented 7 years ago

have you found any solutions for it

JarrenJ commented 7 years ago

Unfortunately no. I have tried re-downloading files, uninstalling and restarting, etc. My guess is that theres a problem with the newdev branch because thats where I download it from, yet nothing changes. -- So, no. no fix yet.

JarrenJ commented 7 years ago

scootcam, I found a solution. Download the cmake folder from here: https://github.com/mattanger/ckb-next/tree/cmake and run quickinstall. It might ask you to download more tools for xcode, if so say yes as you will need them. If you need any additional help just reply back to me.

ghost commented 7 years ago

@scootcam @JarrenJ the cmake branch is the development one and is not ready to be used, please use the testing one next time. This is just the coincidence that both cmake and testing branches have the same files that won't break your setup, but still. The project is going to refactor the Readme file for easier troubleshooting and current project status.

JarrenJ commented 7 years ago

Thanks for the info.

Sent from my iPhone

On Jan 21, 2017, at 3:10 PM, Oleksii Vilchanskyi notifications@github.com wrote:

@scootcam @JarrenJ the cmake branch is the development one and is not ready to be used, please use the testing one next time. This is just the coincidence that both cmake and testing branches have the same files that won't break your setup, but still. The project is going to refactor the Readme file for easier troubleshooting and current project status.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.