I’m trying to compile a release version of Chromium 1.9 by using Cygwin on windows XP. However the process stops or rather hangs when it reaches the compilation of pixel.c (one of the files in the Util library) and never finishes. When I compile in debug mode (RELEASE=0 in options.mk) there is no problem and everything compiles fine.
What is the difference in pixel.c for these two compiling modes and does it have any significant impact on Chromium’s performance which mode I use?
Regards
- Jakob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well… I’ve solved my problem and all I had to do was wait. :) The compiling process hadn’t got stuck at all. It just took a long time. In fact it to me 27 minutes to compile it all but the compiler used 21 of them on the pixel.c file. Some heavy optimization going on I guess. :)
- Jakob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I’m trying to compile a release version of Chromium 1.9 by using Cygwin on windows XP. However the process stops or rather hangs when it reaches the compilation of pixel.c (one of the files in the Util library) and never finishes. When I compile in debug mode (RELEASE=0 in options.mk) there is no problem and everything compiles fine.
What is the difference in pixel.c for these two compiling modes and does it have any significant impact on Chromium’s performance which mode I use?
Regards
- Jakob
Well… I’ve solved my problem and all I had to do was wait. :) The compiling process hadn’t got stuck at all. It just took a long time. In fact it to me 27 minutes to compile it all but the compiler used 21 of them on the pixel.c file. Some heavy optimization going on I guess. :)
- Jakob