Installed to root of drive, reset all environment paths, and all problems went
away. I think it was having problem with long pathname. :/
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to th
This must have been asked before but can't find an explanation so ... just
curious why Exception::Error et al are declared to have a Local
result instead of Local. A not uncommon pattern is to create a new
Error object and then set some properties on it which requires a ->ToObject
or Local::Cas
Well, please double-check for typos. If you look around
File "C:\Users\JH\Documents\Libs\depot_tools\v8\build\vs_toolchain.py",
> line 40, in SetEnvironmentAndGetRuntimeDllDirs
you'll see that a few lines before it checks for that environment variable,
and won't proceed to the code that later
No.
On Monday, February 8, 2016 at 7:15:10 AM UTC-8, Jakob Kummerow wrote:
>
> On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington > wrote:
>
>>
>>> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8
>>> -Dtarget_arch=x64 -Dcomponent=shared_library
>>> Please follow the instructions at
No.
On Mon, Feb 8, 2016 at 7:14 AM, Jakob Kummerow
wrote:
> On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington
> wrote:
>
>>
>>> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8
>>> -Dtarget_arch=x64 -Dcomponent=shared_library
>>> Please follow the instructions at
>>> http://www.ch
On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington
wrote:
>
>> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8
>> -Dtarget_arch=x64 -Dcomponent=shared_library
>> Please follow the instructions at
>> http://www.chromium.org/developers/how-tos/build-instructions-windows
>>
>
That link
>
>
> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8
> -Dtarget_arch=x64 -Dcomponent=shared_library
> Please follow the instructions at
> http://www.chromium.org/developers/how-tos/build-instructions-windows
> Traceback (most recent call last):
> File "v8\build\gyp_v8", line
Are you looking for
https://github.com/v8/v8/wiki/Building%20with%20Gyp#building-1?
On Mon, Feb 8, 2016 at 10:18 AM, Joe Harrington
wrote:
> Followed the instructions on the page and have yet to get to where it
> makes the build files. :(
>
> --
> --
> v8-users mailing list
> v8-users@googlegrou
Followed the instructions on the page and have yet to get to where it makes the
build files. :(
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsu
How did you check out V8? Did you follow the instructions at
https://github.com/v8/v8/wiki/Using%20Git#how-to-start?
(My guess would be that you simply "git clone"d the main repository. Doing
so wouldn't run "gclient sync", so you'd end up missing all third-party
dependencies, one of which is tool
That's just how GYP behaves. FWIW, our documentation reflects this, see the
command line in
https://github.com/v8/v8/wiki/Getting%20Started%20with%20Embedding#run-the-example
.
(Also, to be fair, "scatters libraries all over" is a bit of an
exaggeration -- V8's libraries are in obj.target/tools/gy
Thanks Yang,
I didn't realize that filing an issue is the preferred way of dealing with
this. In hindsight that seems obvious. Will do in the future should
anything else come up.
On Sunday, February 7, 2016 at 11:35:39 PM UTC-8, Yang Guo wrote:
>
> Hi,
>
> this feature request sounds reasonable
12 matches
Mail list logo
