The particular problem you're running into is that it can't find an installation of bison on your system, which is one of the many components needed to build WebKit. I only ever tried compiling under OS X, and had a report from someone else that was encountering this problem on Linux. I'm not sure how to fix it without looking into the issue further.
I actually abandoned this project a long time ago and switched to iOS, because I realised it was simply too hard to get a custom WebKit build working with Android, since their build system and the way they've done the port is such a mess. After spending a full 10 days just trying to get the thing to compile, I realised that I was going to have to write a large amount of extra glue code to get it working properly.
Things may have improved somewhat since the 4.0 release, as it's open source - this was done back in the dark days of Honeycomb where they had temporarily un-open sourced the project and I faced the prospect of having to do my own reimplementation of the closed source parts of the glue code (i.e. the Java side of things), which was going to be a huge amount of effort. At the time it was not clear whether they were planning to open up the source again, but it's good that they did, so this may be easier now.
I recommend contacting one of the Android development lists to find out what the current status of WebKit is and whether or not they've made it possible to built WebKit separately from the main source tree. I haven't been keeping up with this since I abandoned the platform more than a year ago.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this issue can be fixed by installing bison on your linux host ( via "sudo apt-get install bison" for example) and adding the following line in the build.sh script:
export HOST_OUT_EXECUTABLES=/usr/bin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi tanya Liu:
I came accros the same problem with you，so have you ever solve the problem.
Hi,
The particular problem you're running into is that it can't find an installation of bison on your system, which is one of the many components needed to build WebKit. I only ever tried compiling under OS X, and had a report from someone else that was encountering this problem on Linux. I'm not sure how to fix it without looking into the issue further.
I actually abandoned this project a long time ago and switched to iOS, because I realised it was simply too hard to get a custom WebKit build working with Android, since their build system and the way they've done the port is such a mess. After spending a full 10 days just trying to get the thing to compile, I realised that I was going to have to write a large amount of extra glue code to get it working properly.
Things may have improved somewhat since the 4.0 release, as it's open source - this was done back in the dark days of Honeycomb where they had temporarily un-open sourced the project and I faced the prospect of having to do my own reimplementation of the closed source parts of the glue code (i.e. the Java side of things), which was going to be a huge amount of effort. At the time it was not clear whether they were planning to open up the source again, but it's good that they did, so this may be easier now.
I recommend contacting one of the Android development lists to find out what the current status of WebKit is and whether or not they've made it possible to built WebKit separately from the main source tree. I haven't been keeping up with this since I abandoned the platform more than a year ago.
I think this issue can be fixed by installing bison on your linux host ( via "sudo apt-get install bison" for example) and adding the following line in the build.sh script:
export HOST_OUT_EXECUTABLES=/usr/bin