Skip to content
This repository was archived by the owner on Dec 4, 2023. It is now read-only.

Conversation

cowboyd
Copy link
Collaborator

@cowboyd cowboyd commented Jul 3, 2015

This upgrades to the 4.5 build process which uses the Chromium depot tools.

This completely removes the v8 source as a submodule and instead uses fetch and gclient sync to configure all build dependencies.

@cowboyd
Copy link
Collaborator Author

cowboyd commented Jul 13, 2015

Sheesh. I'm the guy who fights always fights with the v8 build and ends up on the floor unconsious.

There is a standalone_static_library option referenced in gyp/generators/make.py, that can be turned on somehow. I thought I'd figured it out, but apparently not. If we can somehow turn that on, then we can actually build linux binaries.

@ignisf
Copy link
Collaborator

ignisf commented Jul 13, 2015

It was a tough one...

-rw-r--r--  1 ignisf ignisf  10M 13 юли 15,29 libv8-4.5.95.5-x86_64-linux.gem

@cowboyd
Copy link
Collaborator Author

cowboyd commented Jul 13, 2015

You magnificent bastard.

you got me you beautiful bastard _c79b658e8e1f7e21575aa9d9e7533b56

Instruct GYP to create a standalone static library
@cowboyd
Copy link
Collaborator Author

cowboyd commented Jul 13, 2015

I noticed with this change, that it puts the archives in the main product dir, just like on darwin, and freebsd, so no need to check in two places for the object files, which was a hack to begin with.

I think we're getting damn close to master here.

* doing a full clone of the depot tools. I thought that I could save
  some time, but it means that building the binaries is not idempotent
* using rvm instead of system ruby
@cowboyd
Copy link
Collaborator Author

cowboyd commented Jul 13, 2015

So after the remaining 2 PR's is there any work left to do before merging to master?

@ignisf
Copy link
Collaborator

ignisf commented Jul 13, 2015

What I think would be nice is to package only the needed sources in the source distribution of the gem and not execute depot tools when it's installed. IIRC the patcher needed to be executed upon installation because there are environment-specific patches that need to be applied. The source however is the same for everybody.

This does not stop us from merging into master.

@ignisf
Copy link
Collaborator

ignisf commented Jul 13, 2015

Disregard that.. This would break using with gem ... github: ...

@cowboyd
Copy link
Collaborator Author

cowboyd commented Jul 13, 2015

Believe it or not, I actually tried that at first, but

  1. All the crap depot tools pooped into vendor/v8 was something like 125M
  2. the build lost its mind when it found that vendor/v8 was not a git repot.

@mintrigue
Copy link

Is this upgrade dead?

@jarredholman
Copy link
Contributor

On the windows side of things, getting the build working is a nightmare.

@ignisf ignisf merged commit 0b97c04 into master May 13, 2016
@ignisf ignisf deleted the 4.5 branch May 13, 2016 20:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants