How to make chromium executable

727 views
Skip to first unread message

jeanba wenceslas

unread,
Jan 11, 2017, 12:59:35 PM1/11/17
to Chromium-dev
I have already made the chromium source code modification, how to do chromium executable.I work under ubuntu 14.04. So I follow the installation chromium under linux.
someone can help me?

PhistucK

unread,
Jan 12, 2017, 2:33:37 AM1/12/17
to jeanba wenceslas, Chromium-dev


PhistucK

On Wed, Jan 11, 2017 at 7:59 PM, jeanba wenceslas <wence...@gmail.com> wrote:
I have already made the chromium source code modification, how to do chromium executable.I work under ubuntu 14.04. So I follow the installation chromium under linux.
someone can help me?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

jeanba wenceslas

unread,
Jan 12, 2017, 2:52:10 AM1/12/17
to Chromium-dev
Yes, I have already built with this command $ ninja -C out / Default chrome.
It works fine, but my question how to have an installable version.
For my browser named "dev_smart". All it works in chromium. And the file size is too large in chromium 983M0. If I see other browser like firefox, google chrome and vivaldi just about 70MO the executable.
My goal: - have a personal browser named "dev_smart"
              - have a dev_smart.exe, dev_smart.tar.gz, or dev_smart.sh version

PhistucK

unread,
Jan 12, 2017, 2:54:39 AM1/12/17
to jeanba wenceslas, Chromium-dev
You will not have an .exe file, because Linux does not use .exe files (as far as I know).

I am not sure about an installer, sorry.

Regarding the file size, you probably built a debug version, try out/Release instead of out/Default, perhaps.
(Or maybe wait for other people to respond, as building takes time)


PhistucK

--

Sidney San Martín

unread,
Jan 18, 2017, 11:19:20 AM1/18/17
to jeanba wenceslas, PhistucK, Chromium-dev

If out/Release doesn’t exist, you can create it by running this command:

$ gn args out/Release

A file will appear in a text editor, replace its content with this:

is_debug = false

You can also out/Release/args.gn in any text editor, and then run this command:

$ gn gen out/Release

When you build with this directory, it should be smaller/faster.

Asesh Shrestha

unread,
Jan 19, 2017, 10:33:20 PM1/19/17
to Chromium-dev
Don't know if it will work on Linux but on Windows I use: "ninja -C out\OutFolder mini_installer" to create a installer

jeanba wenceslas

unread,
Jan 20, 2017, 4:09:55 AM1/20/17
to Chromium-dev

Thank you very much, but they can be effective, and I will make them to proceed row. I made an attempt for chromium android with the following command:


chromium/src$ . build/android/envsetup.sh

chromium/src$ third_party/android_tools/sdk/platform-tools/adb devices
this
error  out:

db devices
List of devices attachedV160XX560900803 no permissions (verify udev rules); see [http://developer.android.com/tools/device.html]

What is likely to be the solution?

David Turner

unread,
Jan 20, 2017, 5:23:52 AM1/20/17
to wence...@gmail.com, Chromium-dev
Have a look at the section that starts with "If you're developing on Ubuntu Linux, ..." on the web page you just listed.
Reply all
Reply to author
Forward
0 new messages