Forgot to update completions for renderBase64
Merge pull request #281 from detro/master

Forgot to update completions for renderBase64
ChangeLog fix: it's onPrompt and not onAlert.

Thanks to Ryuichi Okumura <okuryu@gmail.com> for the notice.

http://code.google.com/p/phantomjs/issues/detail?id=598
Don't build the deploy in debug mode.

Debug mode turns off all optimisations. This make PhantomJS considerably
slower.

Instead, we build in 'release' mode, but generate debugging symbols at
the same time.

This may present some problems analysing crashes, if the optimisations
make that difficult. However, in my testing I was able to get useful
debug output even with optimisations enabled. So we should see how we go
- if it becomes a problem we can produce seperate debug binaries with no
optimisations.

https://code.google.com/p/phantomjs/issues/detail?id=599
Fix symbols generation on Linux

We are linking against e.g. libQtCore.so.4 rather than
libQtCore.so.4.8.2, and this affects symbol generation. (I am not sure
if this changed at some point, but this change should make it generate
the correct symbol files regardless.)

Also makes it less dependent on the Qt version.
Fix the top-level folder name in the packaged symbol tarball.
Use zip for the OS X package

Requested by @ariya, who was concerned that .tar.bz2 might be confusing to
OS X users who are not well-versed in UNIX.
Merge pull request #284 from jonleighton/deploy2

Deploy fixes
Bumping version to "1.7.0 (development)"
Merge pull request #289 from detro/master

Version bump
Merge branch 'master' of github.com:ariya/phantomjs
Fix remote inspector when building statically.

For some reason, it seems that checking CONFIG(static) inside
src/phantomjs.pro is not reliable. That caused the STATIC_BUILD define
not to be set, and hence Q_INIT_RESOURCE would never get called in
main.cpp.

Instead of using Q_INIT_RESOURCE, let's just compile the resources
directly into the phantomjs binary. This means we don't need to detect
whether Qt is linked statically or dynamically.

https://code.google.com/p/phantomjs/issues/detail?id=430
Merge pull request #291 from jonleighton/static_inspector

Fix remote inspector when building statically.
Merge branch 'master' of github.com:ariya/phantomjs
Increase VM memory. Necessary for linking on 64-bit build.

http://code.google.com/p/phantomjs/issues/detail?id=599
Deploy script improvements.

http://code.google.com/p/phantomjs/issues/detail?id=599

Squashed commit of the following:

commit 2cdcf8a47567f3c067958383843cccf858af531c
Author: Jon Leighton <j@jonathanleighton.com>
Date:   Sat Jul 7 19:37:38 2012 +0100

    Make lib-bundling/brandelf optional in deploy/package.sh

    This configuration has had some problems and we don't wish to use it in
    the official packages.

    Enable it with --bundle-libs.

commit 2a2155a4e1f5873aa8624859cead9d66750747f4
Author: Jon Leighton <j@jonathanleighton.com>
Date:   Sat Jul 7 19:24:40 2012 +0100

    notify user if upx is missing

commit 9656a99df0ff101150276dc88e0127f68041f617
Author: Jon Leighton <j@jonathanleighton.com>
Date:   Sat Jul 7 19:23:36 2012 +0100

    stripping symbols after upx probably doesn't work, reorder that

commit c5f425dc17069c89e7d2ff274309006c728ffab4
Author: Jon Leighton <j@jonathanleighton.com>
Date:   Sat Jul 7 19:17:07 2012 +0100

    fix logical fail
Add require() tests and comment buggy test in fs-spec-03.js

http://code.google.com/p/phantomjs/issues/detail?id=47
Merge phantomjs-nodify's require() and fix tests

Most of the tests passed after merging almost unchanged phantomjs-nodify
code, some needed small changes. The one that is still failing is for
CoffeeScript modules.

http://code.google.com/p/phantomjs/issues/detail?id=47
Add test for .stack in errors thrown in modules

We want to be sure that the stack contains module file path.

http://code.google.com/p/phantomjs/issues/detail?id=47
Add Phantom::loadModule

Instead of trying to use sourceId to determine what module threw an
error, we now load module's source code using modified
QWebFrame::evaluateJavaScript and leverage PhantomJS's stack traces.

http://code.google.com/p/phantomjs/issues/detail?id=47