-
Notifications
You must be signed in to change notification settings - Fork 614
Conversation
use correct fs.symlink on mac and linux add arch support for linux 64-bit update grunt tasks for linux add linux installer to grunt tasks fix linux clean installer task update grunt for node on linux. move linux tools to an npm postinstall script. rename debian package to Brackets Sprint NN.deb fix 64 bit build update debian package version and 64-bit dep
…pendencies via their package managerprior to running grunt build
…be/brackets-shell into jasonsanjose/linux-sprint-29 Conflicts: installer/linux/build_installer.sh
@@ -114,7 +126,7 @@ module.exports = function (grunt) { | |||
"files": [ | |||
{ | |||
"expand" : true, | |||
"cwd" : "out/Release", | |||
"cwd" : "out/Release/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasonsanjose what's the significance of this change? I noticed that we mostly put the trailing slash on directory names but there are a few instances where we don't. Just curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for consistency. I thought this was the last oddball. Was there more?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least 4 other places have directory names that do not end in a forward slash. Probably not a big deal -- I was just curious if Linux had some special requirement.
I got an error running grunt on Windows "ERROR: Cannot find module 'semver'" but grunt continues and finishes the build. Haven't tried Mac yet. |
Same error on Mac |
Conflicts: Gruntfile.js
Updated the pull request description to run |
@@ -0,0 +1,39 @@ | |||
#!/bin/sh | |||
# | |||
# Copyright (c) 2009 The Chromium Authors. All rights reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to add to 3rd party code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to wait for legal before merging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll ping @julianasuh. The source is from Chromium's debian packaging scripts here http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/linux/.
Windows now builds without error |
…it linux due to missing 3.1547.1354 binary.
…obe/brackets-shell into jasonsanjose/linux-sprint-29
No problem with the npm install but I'm failing on the cef-download task with a |
@timburgess downloads are fixed now. @adrocknaphobia thinks it could have been a bot. Anyway, @JeffryBooher pointed out 2 issues over email that I've filed. We can fix these separately from this pull request:
|
Yup, I can see dev.brackets.io now. The same as master, the CEF version for cef-linux64 has bumped to 3.1547.1354 yet there is no cef_binary_3.1547.1354 on dev.brackets.io/cef so the cef task fails on 64-bit Linux. I see also that cef-linux32 has CEF 3.1547.1357 hardwired & that is not present on dev.brackets.io/cef either. I've been working on Linux with prior CEF builds I did myself. Will see if I can get a CEF 3.1547.1357 build via chromium & if so, then can at least test the latter stages too. |
Ah, missed the comment - ignore the CEF 32bit vs 64bit version question. |
@timburgess yep we had to hardcode the 32-bit binary since build 1354 wasn't built. This is just temporary until we make our next CEF upgrade. The zips were just pushed to dev.brackets.io/cef. You can try that out now. |
Lovely! Works for me but I had a couple of hitches:
and to clarify, this is on Ubuntu 12.04 64bit |
Looks like everything is good to go -- just waiting to hear back from legal on the 3rd party code. |
Got clearance from legal...Merging |
Replaces #288 @JeffryBooher
Replaces
scripts/setup_linux_build.sh
.RUN npm install on this branch to update the new dependency on
semver
.@timburgess @DaBungalow would you like to test out these updates? Someone else with committer rights will need to handle merging though.
These changes bring the Linux setup and build Grunt tasks up to par with mac and windows. This doesn't replace the one-line
wget
(see https://gist.github.com/jasonsanjose/5514813) required for downloading the git repositories and installing Node.js and Grunt.Here are the highlights:
Debug
folder. For folks like @timburgess that are doing work with the native shell, it won't be too hard for them to get the full binaries manually.grunt
to setup and build.grunt installer
will produce the debian packagepostinstall
hook afternpm install
to install the compile-time dependenciesgrunt build
or simplymake
as beforeDEBIAN\control
file and populate dynamically with brackets version, arch and installed size. See Lintian error: Split linux debian installer CONTROL file for 32 and 64 bit brackets#4724.