Re: [chromium-dev] License implications on Chromium's design
On Mon, Jan 18, 2010 at 6:07 PM, Jerome Leclanche wrote: > Hi people > I'm currently writing an IM client in C++ with Qt. I'm basing the entire UI > strongly upon the Chromium philosophy - tabs on top, no menus, one global > url bar, a new-tab page, so on. > Before opening up the code base, I want to know what the implications are, > license-wise. Ideally, the project would be released under BSD or MIT. Are you using chromium code, or just creating a UI that looks like chromium's UI? Sam > Spare some advice :-) > > J. Leclanche / Adys > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] Re: Incorrect files under "\src\third_party\python_24"?
Before python 2.5, a try block could not have both an except and finally block. (See http://docs.python.org/reference/compound_stmts.html#the-try-statement). In pre-2.5 python, you can get around this using two nested try blocks. try: try: blah() except: yada() finally: something() So there are two ways to resolve this: Use a newer version of python, or change the code to use two nested try blocks. Sam On Mon, Mar 9, 2009 at 1:05 AM, gutongsedeyo...@gmail.com < gutongsedeyo...@gmail.com> wrote: > > 1) I am trying to compile Chromium with hammer/scons on Windows, with > the latest source, and I am getting the following error message: > > scons: Reading SConscript files ... > File "D:\chromium\src\tools\grit\grit\scons.py", line 83 > > finally: > > ^ > > SyntaxError: invalid syntax > > 2) I looked into the "\src\tools\grit\grit\scons.py" file, find a "try- > except-finally" branch around line 83 mentioned in the error message. > > 3) I tried to write a test Python script, both "try-except" and "try- > finally" works, however when I wrote "try-except-finally" I got the > same error message like above. Download python 2.6 and run the "try- > except-finally" test again, it works fine! > > Maybe some files under "\src\third_party\python_24" are incorrect? > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Writing tips to our build instructions?
Hironori, Good catch. I updated http://code.google.com/p/chromium/wiki/MacBuildInstructions with the following text: The path to the build directory should not contains spaces (e.g. "~/Mac OS X/chromium"), as this will cause the build to fail. Sam On Mon, Feb 16, 2009 at 11:57 PM, Mohamed Mansour wrote: > Hey there, > This wiki is open to anyone to edit, > http://code.google.com/p/chromium/wiki/MacBuildInstructions > > It is linked directly from: > http://dev.chromium.org/developers > > I have seen the IRC log :) Many people are having this issue, would be > great to update it so future coders wont run into the same problems. > > > > On Mon, Feb 16, 2009 at 11:54 PM, Hironori Bono (坊野 博典) < > hb...@chromium.org> wrote: > >> >> Hi Chromium developers, >> >> Today, I noticed a person who could not build Chromium (on Mac OS X) >> because he/she downloaded the source code of Chromium to a directory >> which contains space characters (e.g. "~/Mac OS X/chromium"). Even >> though I'm not sure this is a known issue, I would like to note this >> to somewhere in our build instructions if not. >> Is it possible to give me good places to write such build tips? >> >> Regards, >> >> Hironori Bono >> E-mail: hb...@chromium.org >> >> >> > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
