-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] Mac OSX 10.9 Support? #3905
Comments
Comment by redmunds
|
Comment by ghost Startup is slower than Win 7 by 2 or 3 seconds, but other than that everything seems to be working OK. |
Comment by redmunds Thanks, Tom. Did you do this testing with Brackets from an installer, or did you clone Brackets and do a local build of brackets-shell? |
Comment by ghost I did it with an installer, however I can do a local build if you want the bleeding edge result? |
Comment by redmunds I was more curious if there were any issues with building brackets-shell with Xcode on Mac 10.9. |
Comment by gruehle Reviewed, low priority to |
Comment by ghost
|
Comment by redmunds That would be great. After you build on Mac 10.9, also be sure that you can run it :) |
Comment by ghost Everything works perfectly fine, built it without a sweat and it's runs fine. Although, it does still lag on start-up. We're still tagging around that 0.7s-1.0s start-up time. |
Comment by njx Yeah, we haven't done any startup optimization yet--we aren't even doing things like precompiling/minifying our JS or LESS files. A long time ago I did a quick prototype of that and it improved startup time by about 20%--might be even more now. |
Comment by ghost
Strangely, the cloned ver. starts up quicker than the installer I downloaded from the Brackets site. I'm not too sure why that might be, so you guys might want to take a geez at that too. -T |
Comment by njx I just did it manually--ran the command-line LESS compiler and substituted in the built version, and used r.js to concatenate/minify all the core require modules (extensions would have to be dealt with separately; for now it's probably fine to just keep them unminified). The right thing to do would be to build all this into the grunt script, of course :) |
Comment by ghost Alright, I might look into that and see if it makes the start-up smoother. If it does, there must be a way to do that automatically. I'll investigate. |
Comment by TuckerWhitehouse Just installed the last OS X 10.9 Preview (v5) and Xcode5-DP5, and can't compile brackets-shell. The grunt output is rather unhelpful (Error Code: 65), but the file it points to (appshell_extensions_mac.mm) appears to have a few issues when the project is opened in Xcode.
The 5th argument being positionIdx, which is defined as an NSInteger and then supplied to the function which expects an int32. Changing the positionIdx definitions from |
Comment by ingorichter Yes, I saw this issue too. |
Comment by ingorichter Since the compile issues happen on 10.8.x too, I don't think that this a 10.9 only issues anymore. |
Comment by martineno I dug into this a little bit and as far as I can tell it seems like XCode 5 defaults to 64-bit target. So when you make the changes that are mentioned by My XCode wrangling skills are weak, but to my inexpert eyes it looks like changing the xcodeproject file to 32-bit target might fix the issue. |
Comment by cfjedimaster Just chiming in that I ran into this as well. OSX 10.8.X with XCode 5 installed (final version). |
Comment by TuckerWhitehouse On OS X 10.8.5 with XCode 5, I have no trouble compiling. If i'm not mistaken, chrome is 32-bit only, so attempting to compile as a 64-bit, as mentioned by |
Comment by cfjedimaster I just switched my XCode back to 4.(um, whatever it was) and it worked fine after that. |
Comment by TuckerWhitehouse Possible Fixes #5328 |
Comment by redmunds The Xcode 5 issue was fixed with pull adobe/brackets-shell#338, so closing this one. |
Issue by ghost
Thursday Jun 13, 2013 at 20:58 GMT
Originally opened as adobe/brackets#4220
Just wondering if the team have starting testing with Maverick? If you guys haven't, I can start looking into things on it and stress-testing it and what-not.
The text was updated successfully, but these errors were encountered: