This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
See http://wiki.winehq.org/BuildAndTestChromium for easy instructions on how to do this. - Dan
On 5 February 2010 01:54, Dan Kegel dank@kegel.com wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
Google seriously needs to depend on system libraries rather than build the whole damned thing themselves. I can forgive them for rolling their own webkit, but with gigabytes of space required to compile and almost 2 hours on that high-speed quadcore ... No, they're doing something wrong.
In other news, well done with getting it to work!
See http://wiki.winehq.org/BuildAndTestChromium for easy instructions on how to do this.
- Dan
Oh, and the build is slow because it's in wine. It builds about three times faster on windows.
On Feb 4, 2010 7:11 AM, "Ben Klein" shacklein@gmail.com wrote:
On 5 February 2010 01:54, Dan Kegel dank@kegel.com wrote:
This message is being sent in gmail in...
Google seriously needs to depend on system libraries rather than build the whole damned thing themselves. I can forgive them for rolling their own webkit, but with gigabytes of space required to compile and almost 2 hours on that high-speed quadcore ... No, they're doing something wrong.
In other news, well done with getting it to work!
See http://wiki.winehq.org/BuildAndTestChromium for easy instructions on how to do this.
- Da...
Dan Kegel wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
See http://wiki.winehq.org/BuildAndTestChromium for easy instructions on how to do this.
- Dan
Cool...
I'll have to try this sometime.
Chip
Dan Kegel wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
w00t!
On 2/4/2010 17:54, Dan Kegel wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
See http://wiki.winehq.org/BuildAndTestChromium for easy instructions on how to do this.
- Dan
Congrats!
Currently only http://bugs.winehq.org/show_bug.cgi?id=19502 prevents a clean install in Wine?
On 4 February 2010 14:54, Dan Kegel dank@kegel.com wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
Nice work.
Do you have any idea of how long it takes to build on native Windows (for a comparison)?
- Reece
On 2/4/2010 18:24, Reece Dunn wrote:
On 4 February 2010 14:54, Dan Kegeldank@kegel.com wrote:
This message is being sent in gmail in Chromium running on Wine with options --no-sandbox --use-nss-for-ssl.
(--use-nss-for-ssl turns on a new alternate https stack that works in wine.)
This copy of Chromium was built in Wine, too. It took 1 hour 55 minutes to compile and link from scratch using Visual C++ 2005 in Wine on a q9300. (And that's compiling with /MP to use all cores; wthout /MP, it takes three and a half hours, IIRC.)
Nice work.
Do you have any idea of how long it takes to build on native Windows (for a comparison)?
This bug http://bugs.winehq.org/show_bug.cgi?id=21423 is about it. Looks like it's about three times slower or so.
- Reece
-
Ben Klein -
Charles Davis -
Dan Kegel -
Jeremy White -
Nikolay Sivov -
Reece Dunn