libcef file size is different from standard distribution ver

[BensonLi]

I follow official guide to build libcef.dll on 6099.234. But the binary size is much smaller than the standard distribution version.
standard distribution version size:162MB
My version size:90.4MB
The link I follow is https://bitbucket.org/chromiumembedded/cef/wiki/MasterBuildQuickStart.md
The main args like below:

update args:
set GN_DEFINES=is_component_build=true
set GN_ARGUMENTS=--ide=vs2022 --sln=cef --filters=//cef/*
python3 ..\automate\automate-git.py --download-dir=c:\code\chromium_git --depot-tools-dir=c:\code\depot_tools --no-distrib --no-build --branch=6099

create args:
set GN_DEFINES=is_component_build=true
set GN_ARGUMENTS=--ide=vs2022 --sln=cef --filters=//cef/*
call cef_create_projects.bat

When I replace the libcef.dll in my application(using cef sharp 120.2.70(6399.234)) with my version, there is one exception raised and showing other dependent module are needed.
The distribution version get from the nuget works well. It seems that distribution version linked more static libraries in it self or something like that.

I want to know are there any settings different between my build version and official standard distribution version. How can I build my version like the distribution version?

[magreenblatt]

For official builds follow the instructions at https://bitbucket.org/chromiumembedded/ ... figuration

[BensonLi]

It can build a official version following the guide now.
However, there is an error when build Debug X86 sandbox version.
Are there any options that I can use to skip building the sandbox version since it break the whole process. I do not need the sandbox version.
Please refer to the attachment.

BTW: Manually to build the release version is ok.

thanks.

[ndesktop]

It's the mising limits include issue. It has been recently discussed on forum (and fixed, if I remember well).

[magreenblatt]

Fixed in https://bugs.chromium.org/p/chromium/is ... id=1503397

[BensonLi]

That's really helpful.
There is no other questions.

Thanks again.