Hello,

I just wanted to add that I successfully compiled v8 today on Windows with 
clang-cl. I also tested the hello world sample, which worked.

I used the following config:
is_debug = false
target_cpu = "x64"
use_custom_libcxx = false
v8_monolithic = true
v8_use_external_startup_data = false
is_clang = true

And I had to add a line to build/config/win/BUILD.gn to silence c++20 
deprecation warnings (which are treated as errors), specifically I added:

cflags += [ "/D_SILENCE_ALL_CXX20_DEPRECATION_WARNINGS" ]

at line 95 (other places would work as well).

Finally, in Visual Studio, I added the include directory and the obj 
directory to their respective places, switched the linker to /MT and linked 
to v8_monolith.lib
dbghelp.lib
Winmm.lib

Note that when I tried using libplatform or libbase I got errors, but 
v8_monolith alone is sufficient. I tried compiling without dbghelp.lib and 
winmm.lib but got errors relating to unresolved symbols that went away when 
I put them back in (there is nothing in the project except the .cpp file 
that I copy/pasted from the hello world sample).


On Monday, November 4, 2024 at 9:26:09 AM UTC-8 Pradish wrote:

> *v8_monolith.lib* is a self-contained and doesn't require linking with 
> other v8 libraries
> it includes all components (v8_libbase,v8_libplatform, v8_init.lib ..etc) 
>
> On Mon, Nov 4, 2024 at 10:13 PM Ion Filipski <armag...@gmail.com> wrote:
>
>> Hi, it worked and rebuilt *v8_monolith.lib* only. But it was on 
>> subdirectory *obj*. And it probably always was there, but I haven't 
>> noticed it, *because it was in obj subdirectory*.
>> Other libraries that were there before were
>>
>> *v8_libbase.lib**v8_libplatform.lib*
>> *wee8.lib*
>> For debug version goes mostly the same.
>> Please disregard the previous message, it has small, but significative 
>> difference.
>> Thanks
>>
>> On Thursday 31 October 2024 at 07:27:09 UTC+2 prad...@gmail.com wrote:
>>
>>> in the command line are you setting this argument ?  this will create 
>>> the v8_monolith.lib the static library 
>>>
>>> ninja -C out.gn/x64.release *v8_monolith*
>>>
>>> i have used the following in my args.gn
>>> is_component_build = false
>>>
>>> is_debug = false
>>> target_cpu = "x64"
>>> use_custom_libcxx = false
>>> v8_monolithic = true
>>> v8_use_external_startup_data = false
>>> is_clang = true
>>>
>>> On Wed, Oct 30, 2024 at 11:46 PM Ion Filipski <armag...@gmail.com> 
>>> wrote:
>>>
>>>> > you can build the V8 .lib 
>>>> I've tried different ways of building v8, particularly playing with 
>>>> these settings
>>>> v8_static_library
>>>> is_component_build
>>>> v8_monolithic
>>>> None of them generated V8.lib. Other libraries like v8_base also not 
>>>> generated. So, what exactly is the way to create generate V8.lib?
>>>>
>>>> On Thursday 17 October 2024 at 10:57:35 UTC+3 Ben Noordhuis wrote:
>>>>
>>>>> On Wed, Oct 16, 2024 at 9:38 PM Ben Ernst <boi...@gmail.com> wrote: 
>>>>> > 
>>>>> > Is it necessary to use clang for the whole program? 
>>>>>
>>>>> In my (admittedly limited) testing clang-cl is ABI-compatible enough 
>>>>> that you can build the V8 .lib with clang-cl and link it against code 
>>>>> built with msvc. 
>>>>>
>>>>> I suppose you could still run into language constructs in the header 
>>>>> files that msvc doesn't understand or misparses. 
>>>>>
>>>> -- 
>>>>
>>> -- 
>>>> v8-users mailing list
>>>> v8-u...@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 unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to v8-users+u...@googlegroups.com.
>>>>
>>> To view this discussion visit 
>>>> https://groups.google.com/d/msgid/v8-users/e0eb81b3-1742-4aaf-ad67-791353748ca3n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/v8-users/e0eb81b3-1742-4aaf-ad67-791353748ca3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@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 unsubscribe from this group and stop receiving emails from it, send an 
>> email to v8-users+u...@googlegroups.com.
>>
> To view this discussion visit 
>> https://groups.google.com/d/msgid/v8-users/3ecc2aa3-5274-4570-b2f5-279694ff35edn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/v8-users/3ecc2aa3-5274-4570-b2f5-279694ff35edn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/v8-users/b51a3d0d-c895-4740-908b-09c43080a2d0n%40googlegroups.com.

Reply via email to