Home › Forums › Platform Specific › OSX › New build on 10.10
- This topic has 7 replies, 5 voices, and was last updated 7 years, 5 months ago by atom.
-
AuthorPosts
-
March 16, 2016 at 12:00 am #68629
Well it’s been a while and i promised to get things up to date.
A new build will be uploading today, i did this build on 10.10 and latest XCode available on that version. It has a fix for very slow moving components in EDIT mode and all fixes that have been made on other platforms. I’m setting the compatibility flag for 10.7 (OSX Deployment Target) and the Base SDK is 10.10.
I have no idea how this will impact Ctrlr on any version of OSX so any feedback is welcome.
This is done on a VM (i did not buy the real hardware MAC yet)
best regards
March 16, 2016 at 7:46 pm #68639Thanks a lot Atom,
i’ll be giving this a spin in the next coming days.Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
March 17, 2016 at 11:22 pm #68649Thanks Atom. Updated. Runs fine on 10.9.5 both app and AU plug version.
March 17, 2016 at 11:45 pm #68652I was not having success with snapshots on my most basic panels … maybe it’s something I’m (not) doing…
I’m just curious if the compatibility flag could be set to 10.6? I still work on 10.6.8 and still IMHO consider it the last good OS X for pro audio especially on the last good mac pro 5,1 cheese grater tower. If it comes at the expense of loose compatibility for current forget it but I don’t think it should…
Rob
Attachments:
You must be logged in to view attached files.Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
October 10, 2016 at 12:39 pm #70127I’m setting the compatibility flag for 10.7 (OSX Deployment Target) and the Base SDK is 10.10.
I have no idea how this will impact Ctrlr on any version of OSX so any feedback is welcome.
I can’t get the Ctrlr AU plugin to compile from the latest git download. I’m using Xcode 6.3.2 on El Cap 10.11.6, with a 10.7 deployment target and 10.10 base SDK (previously tried Xcode 8.0 (base SDK 10.12), but that caused even more compilation problems).
I managed to get the Wrapper.jucer project to compile and copy the libau_wrapper.a static library to /usr/local/lib; had to create and fix permission problems on that folder (is the wrapper still required now that JUCE includes the CoreAudioUtilityClasses?)
Then I had to fix the path in the ‘post-commit’ script in the ./Scripts folder, from this:
[OSNAME=”OSX”]
CTRLR_ROOT=”$HOME/devel/ctrlr”To my personal ‘ctrlr-master’ root folder:
CTRLR_ROOT=”$HOME/Documents/Programming/Ctrlr”
Running the edited post-commit script then successfully generated the CtrlrRevision.h file.
——
So, after spending 4 frustrating days getting to that stage, the AU plugin won’t compile in Xcode. I get a missing file error for this file:
‘/Users/dan/Documents/Programming/Ctrlr/Source/Misc/lua.c‘
These files are also missing from the ./Lua/luabind/luabind folder:
luaxlib.h
lua.h
lua.hpp
luaconf.h
lualib.hHope someone can help. Wouldn’t want to waste the last 4 days trying to compile Ctrlr 🙂
Thanks..
- This reply was modified 7 years, 5 months ago by danrand.
October 12, 2016 at 2:20 pm #70129The latest git tree will only work with Standalone for now, this is how far i got, windows is Standalone/VST (i posted a build yesterday), mac is Standalone.
I need to re-work all the other projects almost from scratch to get latest lua and other changes to work.
October 14, 2016 at 6:08 am #70134Hi Atom,
after the installation of the newest Win build Ctrlr-5.4.11.exe the Help>About still shows Version = 5.3.201 and Build date = March.30th
Am I doing something wrong or is this how it should be?
Cheers!October 14, 2016 at 4:56 pm #70135it’s possible it was a test release, i’ll give it a second look today, i’m doing Linux stuff right now
-
AuthorPosts
- The forum ‘OSX’ is closed to new topics and replies.