build chromedriver

[kri laz]

hi, 

synced using gclient sync

i get chrome source code.

~/work/src/

tried to build chromedriver  ninja -C out/Release chromedriver 

from "work" folder  (father of src)

ninja: Entering directory `out/Release'

ninja: fatal: chdir to 'out/Release' - No such file or directory

from "src" folder  

ninja: Entering directory `out/Release'

ninja: error: loading 'build.ninja': No such file or directory

any help ?

[Lei Zhang]

"gclient sync" likely never completed successfully. Its last step is
to run gyp, which generates out/Release/build.ninja.

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev

[kri laz]

hi Lei, thank you for your replay,

in effect at the time to execute git after having synchronized chrome, the "Invalid user name or password" error messages

yet I have got a password generated by git

[Thiago Farina]

On Wed, Oct 29, 2014 at 6:42 AM, kri laz <lazh...@gmail.com> wrote:

hi Lei, thank you for your replay,

in effect at the time to execute git after having synchronized chrome, the "Invalid user name or password" error messages

I don't think that has anything to do with the synchronization process.

You usually do:

# Assuming you are on master branch and rebase workflow:

$ git pull --rebase

$ gclient sync

In the end of sync process, it will run hooks, which will call build/gyp_chromium, which will generate the ninja build files.

When it completes successfully, you will be able to see it created out/Debug and out/Release.

After that you should be able to do:

$ ninja -C out/Debug chrome

or 

$ ninja -C out/Release chrome

--

Thiago Farina

[Anantha Keesara]

Kri, If you still have questions, please ping Sam(cced), Chromedriver lead. He can help you build Chromedriver.

--

[Sam Uong]

Kri, there's no difference between checking out Chromium and checking out ChromeDriver, so Thiago's instructions should work. However if you're only interested in building chromedriver, you should do a "ninja -C out/Release chromedriver" instead of "ninja -C out/Release chrome".

[kri laz]

hello Thiago,

thanks for your help, now my synchronise is done before your answer, but when i try your command 

Le mercredi 29 octobre 2014 16:55:10 UTC+1, Thiago Farina a écrit :

On Wed, Oct 29, 2014 at 6:42 AM, kri laz <lazh...@gmail.com> wrote:

hi Lei, thank you for your replay,

$ git pull --rebase

i get this message " fatal: Not a git repository (or any of the parent directories): .git"

i try it from differents level (folder) until "git"

[kri laz]

thanks Anantha.  i ask Sam

[Thiago Farina]

On Thu, Oct 30, 2014 at 8:53 AM, kri laz <lazh...@gmail.com> wrote:

hello Thiago,

thanks for your help, now my synchronise is done before your answer, but when i try your command 

Le mercredi 29 octobre 2014 16:55:10 UTC+1, Thiago Farina a écrit :

On Wed, Oct 29, 2014 at 6:42 AM, kri laz <lazh...@gmail.com> wrote:

hi Lei, thank you for your replay,

$ git pull --rebase

i get this message " fatal: Not a git repository (or any of the parent directories): .git"

i try it from differents level (folder) until "git"

Usually the checkout process will create a folder structure like this:

/path/to/your/chromium/src

Where chromium is the directory that holds the .gclient file used by gclient tool from depot_tools. The 'src' directory will contain your .git directory.

Of course others name the 'chromium' directory whatever they like and put it whatever they want.

But the 'src' should be there somehow and should contain the '.git' directory.

Isn't that your case? How is your directory structure?

Have you bootstraped through the tarball? Instead of using the 'fetch' command?

--

Thiago Farina

[Thiago Farina]

Note that you can get the source code by running:

$ fetch --no-history chromium

-- 

Thiago Farina

[kri laz]

i get the source code only by "$gclient  sync"  ... 

i try now your command fetch --no-history chromium 

i get 

You appear to already have a checkout. "fetch" is used only

my directory structure is :

my-workstation:~/work/src/.git

9.0.600.0     depot_tools selenium   work

my-workstation:~/work$ ls

_bad_scm ninja  src

my-workstation:~/work/src$ ls

Android.mk       build       cloud_print          device         jingle               out                rlz          tools

android_webview  BUILD.gn    codereview.settings  extensions     LICENSE              OWNERS             sandbox      ui

apps             buildtools  components           gin            LICENSE.chromium_os  pdf                sdch         url

ash              cc          content              google_apis    media                ppapi              skia         v8

athena           chrome      courgette            google_update  mojo                 PRESUBMIT.py       sql          WATCHLISTS

AUTHORS          chromecast  crypto               gpu            native_client        PRESUBMIT_test.py  sync         webkit

base             chrome_elf  dbus                 ios            native_client_sdk    printing           testing      win8

breakpad         chromeos    DEPS                 ipc            net                  remoting           third_party

[kri laz]

sorry 

my-workstation:~/

9.0.600.0     depot_tools selenium   work

[Thiago Farina]

On Thu, Oct 30, 2014 at 12:59 PM, kri laz <lazh...@gmail.com> wrote:

sorry 

my-workstation:~/

9.0.600.0     depot_tools selenium   work

I suggest you start from the scratch, with a clean directory.

You could try doing (from ~/):

$ cd work

$ mkdir chromium

$ fetch --no-history chromium

# Wait a couple of hours, let it running through the night for example.

# Go back at morning.

$ ls out

....

--

Thiago Farina

[Thiago Farina]

Btw, does this page, https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code-v2, helps you? 

Regards,

--

Thiago Farina

[kri laz]

ok Thiaggo, i try to do that, tomorrow i will tell you what the result.

lot of thanks for your help 

[kri laz]

i never seen this page and yet I read all the forums .

3 months i try to do generate chromedriver.

fetch still working in chromium folder, tomorrow i will be in day off, monday i will write the result.

thank you so much.

[kri laz]

src synchronise is done but not GYP..

Updating projects from gyp files...

Package libexif was not found in the pkg-config search path.

Perhaps you should add the directory containing `libexif.pc'

to the PKG_CONFIG_PATH environment variable

No package 'libexif' found

gyp: Call to 'pkg-config --cflags libexif' returned exit status 1.

Error: Command /usr/bin/python src/build/gyp_chromium returned non-zero exit status 1 in /home/lkrim/work/chromium

Hook '/usr/bin/python src/build/gyp_chromium' took 17.96 secs

Traceback (most recent call last):

  File "/home/lkri/depot_tools/fetch.py", line 320, in <module>

    sys.exit(main())

  File "/home/lkri/depot_tools/fetch.py", line 316, in main

    return run(options, spec, root)

  File "/home/lkri/depot_tools/fetch.py", line 310, in run

    return checkout.init()

  File "/home/lkri/depot_tools/fetch.py", line 122, in init

    self.run_gclient(*sync_cmd)

  File "/home/lkri/depot_tools/fetch.py", line 76, in run_gclient

    return self.run(cmd_prefix + cmd, **kwargs)

  File "/home/lkri/depot_tools/fetch.py", line 66, in run

    return subprocess.check_call(cmd, **kwargs)

  File "/usr/lib/python2.7/subprocess.py", line 511, in check_call

    raise CalledProcessError(retcode, cmd)

subprocess.CalledProcessError: Command '('gclient', 'sync', '--no-history')' returned non-zero exit status 2

[Sam Uong]

You'll also need to run /path/to/chromium/src/build/install-build-deps.sh to install build dependencies. I think this script is only supported on Ubuntu but if you're running a different distro you could try looking at https://code.google.com/p/chromium/wiki/LinuxBuildInstructionsPrerequisites for instructions.

Once you've installed dependencies, run "gclient sync" again and then "ninja -C out/Release chromedriver".

Sam.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[kri laz]

I can finally build chrome. many thinks for your help, many thanks for your help guys i try it 3 months during 

cheers

[Ethan Lim]

If it is alright, could I submit a patch to include another script for the debian distro.

It's alright to have a specific script for ubuntu but I think we can definitely expand on that for other distributions.

Best Regards
Lim Zhi Hao (Ethan)

[kri laz]

hi Ethan, all of help or experience is welcome

[Sam Uong]

Ethan, I think that support for Debian and other distros in the install-build-deps.sh script, or in a separate script, might be hard to keep up-to-date since the Chromium build infrastructure (and most developer desktops) run Ubuntu. When dependencies get added (or removed) this will happen for Ubuntu but will likely be forgotten for other distros.

If you can convince an owner that this won't become a problem, you might be able to get them to accept these changes. I'll let others weigh in with their opinions if they have any...

Sam.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.