search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Brackets-shell build fails on mac OSX (Mountain Lion) #4905

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by fungl164 Tuesday Sep 24, 2013 at 21:29 GMT Originally opened as https://github.com/adobe/brackets/issues/5328

I used 'npm install' to kickstart the build process and got this error:

... Running "build-mac" task \ BUILD FAILED **

The following build commands failed: CompileC xcodebuild/appshell.build/Release/appshell_helper_app.build/Objects- normal/x86_64/appshell_extensions_mac.o appshell/appshell_extensions_mac.mm normal x86_64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (1 failure)

From XCode, when building the Brackets target, I get this:

/Users/dev/Apps/Brackets-dev/brackets- shell/appshell/appshell_extensions_mac.mm:985:33: No matching function for call to 'getNewMenuPosition'

Anyone knows how to fix this?

Thnxs,

Luis

core-ai-bot commented 3 years ago

Comment by ingorichter Wednesday Sep 25, 2013 at 05:03 GMT

@fungl164 do you use XCode 5? The error happens because XCode "assumes" that you are building on a 64 bit System. I created a branch irichter/fix-xcode5-issues in the brackets-shell repo that resolves this issue. Give it a try. Feedback is welcome.

core-ai-bot commented 3 years ago

Comment by fungl164 Wednesday Sep 25, 2013 at 21:02 GMT

@ingorichter thanxs. I checked out your branch and everything seems to compile and work fine even when launching canary. However, I cannot get the live editing to work on canary even though it re-launches in debug mode (e.g. debug-port = 9222). Any ideas?

core-ai-bot commented 3 years ago

Comment by ingorichter Wednesday Sep 25, 2013 at 21:46 GMT

@fungl164 No, I haven't yet looked at the issues with Chrome Canary. I'll let you know about any findings.

core-ai-bot commented 3 years ago

Comment by redmunds Wednesday Sep 25, 2013 at 21:49 GMT

Brackets doesn't work with Canary. You need Chrome.

core-ai-bot commented 3 years ago

Comment by peterflynn Wednesday Sep 25, 2013 at 21:50 GMT

@fungl164@ingorichter I don't think Live Development is epxected to work with Canary yet. See: https://trello.com/c/MYaUdJOR/508-live-development-w-custom-chrome-install-e-g-canary-or-portable-chrome

core-ai-bot commented 3 years ago

Comment by fungl164 Thursday Sep 26, 2013 at 00:25 GMT

@all so I got Brackets sprint 32 development build 0.32.0-0 (master 844931f1b) to launch canary with live development and it works fine.

Uninstalling Theseus did the trick; though for whatever reason Brackets sprint 31 does not work properly. It now tries to re-launch chrome every time I click on . Perhaps, it's got something to do with sharing data in the App Support folder?? dunno...

If anyone has any ideas on what could be happening here, I'd appreciate it. thnxs.

core-ai-bot commented 3 years ago

Comment by ingorichter Thursday Sep 26, 2013 at 01:38 GMT

@fungl164 Sorry, but the linked commit is something completely different. I'd like to have a look at your changes, but I'm unable to find them.

core-ai-bot commented 3 years ago

Comment by fungl164 Thursday Sep 26, 2013 at 02:43 GMT

@ingorichter sorry for the confusion. I was just pointing out that I'm using the latest commit from the adobe/brackets repo. The only change i've done in adobe/brackets-shell is in "appshell/appshell_extensions_mac.mm"

37 // App ID for either Chrome or Chrome Canary (commented out) 38 //NSString const appId =@"com.google.Chrome"; 39 NSString const appId =@"com.google.Chrome.canary";

then I removed the Theseus extension. I double checked this by installing and uninstalling Theseus a couple of times. I hope this helps. Let me know if you need more info...

core-ai-bot commented 3 years ago

Comment by dangoor Monday Sep 30, 2013 at 18:18 GMT

@fungl164 it looks like the original issue has been handled here, and it's great that you've had progress in getting Canary to work. I'm going to close this issue, however, as Canary support is tracked on our backlog. Feel free to comment there and add a pull request if you do get it working.