Hi again,

  you necessarily don't need different Macs to test the different *apps. If you compile LibreCAD against the different MacOS SDKs then you can make quite sure that things will work (my knowledge from years long porting another *app from Linux to Mac OS in the past). Further, if somebody eg. has Mac OS 10.9 installed he also has "some" libs from older Mac OS systems in the background and can test these too (which identically behaves the same as if you would run it on another machine). When I was running Mac OS 10.6 I was able to compile against 10.4 but also I was able to run the *app like 10.4 (Mac OS 10.9 is too new for me to already have enough experience like I had with Mac OS 10.6).

  You're absolutely right, the better way for the workaround would be to compile it from source. But as a retired developer I won't take the time anymore to dig into such topics. But I'm still here to test your builds and to give some (maybe helpful or not) tips if you need/want them for what can be done to make things better :)

  "My" quick and dirty hack BTW does work to do a little bit of drawing in LibreCAD... But at some points (eg. "print preview") LibreCAD still crashes because of the wrong libmuparser.X.dylib saying that the one or the other function is not found in that dylib - which of course is just correct. Now I'm looking forward to a new LibreCAD.app from you and will report back how things work ;)

Thanks a lot!

  Mogl

---

If you reply to this email, your message will be added to the discussion below:

http://forum.librecad.org/LibreCAD-crashes-on-a-freshh-and-clean-OSX-Mavericks-Workaround-tp5709352p5709355.html

To start a new topic under LibreCAD-dev, email [hidden email]
To unsubscribe from LibreCAD-dev, click here.
NAML