I don’t mean to mis-lead anyone. The issues I”m talking about are part of Audacity 2.1.2. Things like not being able to drag-highlight-scroll right in editing a track, and drag+highlight-dcroll left+edit only works sometimes. There also appears to be something about it that interferes with other running apps, in this case, iBooks running at the same time over the course of about half an hour gets slower and slower to scroll, untill it gives up all together and becomes unusable. If I close down Audacity 2.1.2, and close iBooks, then open iBooks again. It starts working as it should. Start up 2.1.2, and after half an hour there abouts - it caries - back comes the problem with iBooks.
So, I’m not talking about the macports build of Audacity - the current port installed fine, and lives in the macports folder in Applications, although it does read the cfg file in the “default” location of course. Which doesn’t seem to trouble it. . It does however exhibit the same problems with scrolling/editing/highlighting as the Audacity build by the Audacity Developers. And probably other issues that I gave up tracking. AS I said. I’m back on 2.1.1, because it’s at least fully functional for what I want. While I’m thinking of it - does the port install session create a log file anywhere of what it does when “port installing” - I’d like to see what’s happening. I am probably wrong, but I don’t remember it actualy compiling and building the Audacity part. All the rest, but that last bit just flicked by too quickly… > I didn't even look at it, but from what I understand the Xcode project > has the 10.6 SDK hardcoded and it might become tricky to get it to > build under later OSes. (Official build instructions start with tricks > about how to install an ancient Xcode on your machine.) > > What is your main reason/motivation to get the Xcode build working? I’ll probably keep tinkering with this unless someone beats me to it. I would like to get the build going with the XCode project, using the latest versions of the SDK, and XCode etc, because trying to use the now almost ancient 10.6 SDK seems counter productive, and is begging for built in instabilities. Indeed, I haven’t managed to build it with the XCode project even using the 10.6 version either, probably because I have the latest versions of everything installed, and it just doesn’t like 10.6 being there. So the reason/motivation is to “make it work” and remove that pesky hard coding so that updates to XCode and SDKs can be more easily followed and checked in the actual project. I know it’s difficult, but it shouldn’t be im possible, if I can create a “map” or a tree diagram of where and what everything is in Audacity’s base source code. I don’t see a source code map anywhere, and the code it’self is minimally commented. Whick is one thing XCode is good for, Sou can see where everything is at a glance pretty much. Does anyone know exactly what the calls are that require the 10.6 SDK? Shouldn’t it then just be a mission to update that code to the new SDK? anyway, it is interesting if nothing else. Robert > On 26 Feb 2016, at 17:48, Mojca Miklavec <[email protected]> wrote: > > On 26 February 2016 at 18:08, Robert Chalmers wrote: >> Thanks Mojca, >> >> It does compile and install with no problems as you say. However it’s still >> the same 2.1.2 that has it’s own issues (bugs?) that I’m waiting patiently >> to see fixed. But not to worry. > > It could be helpful to point those problems out. Are these upstream > issues or something that's only present in MacPorts? I only use the > most basic features, so I'm unlikely to run into problems. > > I can imagine that the switch from wxWidgets 2.8 to 3.0 introduced a > number of problems. If you can describe the steps to reproduce them > (either in our tracker or even better upstream), we could at least > test and try to figure out if we know how to fix them. > >> I’m pretty impressed by your work getting this to build. > > This was done by René, not by me. > >> I’d love to have >> the time to get it working under XCode with the XCode build. I started with >> it, but collided with a whole lot of issues… > > I didn't even look at it, but from what I understand the Xcode project > has the 10.6 SDK hardcoded and it might become tricky to get it to > build under later OSes. (Official build instructions start with tricks > about how to install an ancient Xcode on your machine.) > > What is your main reason/motivation to get the Xcode build working? > > Mojca Robert Chalmers [email protected] <mailto:[email protected]>.au Quantum Radio: http://tinyurl.com/lwwddov Mac mini 6.2 - 2012, Intel Core i7,2.3 GHz, Memory:16 GB. El-Capitan 10.11. XCode 7.2.1 2TB: Drive 0:HGST HTS721010A9E630. Upper bay. Drive 1:ST1000LM024 HN-M101MBB. Lower Bay
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
