I think, that osx port will be really useful only if there will be audiounit plugin support (and may be vst, but these are rearely used on osx).
> 2015-02-14 13:27 GMT+01:00 Andrew Deryabin <[email protected]>: > > Hi Robert, > > > > > Hi Andrew, > > > > > > 2015-02-14 10:21 GMT+01:00 Andrew Deryabin <[email protected]>: > > > > Hi Robert! > > > > > > > > I’m writing from mac os x 10.10 yosemite. Compiled platform > > > > independence > > > > > > branch without errors (though without any plugins support). > > > > > > Nice :) The mac I have access to is old and only support os x 10.7 but > > > > here > > > > > I can compile with the MESS plugins atleast. > > > > I don't have real mac, so I just downloaded latest hackintosh and > > installed it > > > > :). > > I see, sounds like a good solution :) > > > > I use the cmake setup: > > > cmake ../muse/muse2/ -DCMAKE_BUILD_TYPE=release > > > -DCMAKE_INSTALL_PREFIX=/Users/ddskrjo/muse_release -DENABLE_LV2=NO > > > -DMODULES_BUILD_STATIC=NO > > > > I also use this command, but build type is set to debug. > > > > > I think I specified the Static=NO since I had started to build with > > > > static, > > > > > since I had linking errors. This however does ofcoure not work for > > > > plugins > > > > > so I backtracked and found the missing linker flags needed to allow > > > > linking > > > > > dylibs with external symbols unresolved. > > > > > > > MusE starts only with flag -d, > > > > > > Does it start just after the build? On my system there is a problem with > > > the dylibs again, I have to manually copy them to the bin dir otherwise > > > muse2 won't find them. Probably some cmake or compiler flag missing. > > > > Yes, I had to use export DYLD_LIBRARY_PATH=/path/to/muse/lib/modules > > to make it start. By default libs were not found, though rpath option is > > set > > in cmake compiler options. May be clang just ignores it. > > Ah, I didn't know there was a DYLD version. Then it's possible to start > with added path atleast. > > I should try adapting the synth loading, see if it can load these dynamic > libraries. > > > > but in normal mode I get this error at last (main window opens and the > > > > > > > program closes): > > > > > > > > midi sequencer thread does not start!? Exiting... > > > > > > I do get this error but not all the time, most of the time it starts up > > > > and > > > > > with some debug prints I can see that the threads are running. > > > Apparently there is some threading issue that locks it up somtimes. > > > Be aware that I have ifdefed out all the SCHED_FIFO stuff in this > > > branch, > > > as far as I know it's not supported in OS X. > > > Still I don't think that will cause the threads to misbehave as long as > > > there is no load. I might be wrong. > > > > > > Is it a real mac or a virtual server you are trying on? > > > > First I tried with mac in vmware on linux, but with not much luck, as it > > crashed a lot. After that I just connected another hdd and installed > > hackintosh on it. So it's like a real mac now :). > > > > > > midi sequencer thread does not start!? Exiting... > > > > > > I hadn't noticed the memory lock errors before, I see now I get them > > > too. > > > otherwise I don't see any errors here. > > > > > > Still, there are lots of things not working when building on OS X so I > > > wouldn't hold my breath about using it yet :P > > > The bigget problem I see, which is maybe related to your problem, is > > > > that I > > > > > get no sound and when I press play on the transport it moves a few bars > > > then stops and everything is locked. > > > > When -d flag is set, dummy driver is used instead jack and everything is > > moving right, so it seems, that the reason of all bugs is in jack driver. > > But > > this needs to be checked though. > > Yeah, sounds like a reasonable analysis for the moment. I might do some > more checking tomorrow. > > > Now I can work on this too as I have a mac os installed. Linux in virtual > > box > > will work just fine :) > > Hehe, cool. No worries if you prioritise other things though ;) I expect > this is still a high risk port, but it would be cool and good expansion of > muse user base. > > > > Other big problems I have noticed: > > > - menus are incomplete (I know Qt OSX does some rearranging of the > > > normal > > > menus, this seems to break down) > > > > Yes, I have the same issue - only File and Functions are here. > > > > > - only a few dialogs are possible to open, can't open mixer for instance > > > > > > Reminds me, there's a minor graphical issue in the editors after moving > > > > to > > > > > qt5, when selecting several events with the mouse some of the lines of > > > > the > > > > > drawn box are hard to see. > > > > Need to check this too, as in linux it was all right (may be it's a qt5 > > theme > > that causes this?) > > What I mean is that this happens for me in Linux also, it's a small issue > though, maybe even hard to see. > > Regards, > Robert -- Regards, Andrew ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
