?HasForceDeviceScaleFactor@Display@display@@SA_NXZ could not be located... |
|||
Issue descriptionMake a GYP build of windows mini_installer: 'GYP_DEFINES': 'component=shared_library branding=Chrome build=Official use_goma=1 gomadir="d:\src\goma-win64" dcheck_always_on=1', Then when running mini_installer.exe, I got the following error dialogue: ?HasForceDeviceScaleFactor@Display@display@@SA_NXZ could not be located in the dynamic link library display.dll
,
May 19 2016
This is not repro on a release build for me: component=shared_library chromium_win_pch=1 >ninja -C out\Release mini_installer >out\Release\mini_installer.exe Is your build fully cleaned?
,
May 19 2016
I made a CLEAN GN component build and saw the same issue. Here's my GN args: use_goma = true is_debug = true ffmpeg_branding = "Chrome" proprietary_codecs = true enable_nacl = false goma_dir = "d:\goma\goma-win" is_chrome_branded = true is_component_build = true Maybe this is something new, could you please sync and try again?
,
May 19 2016
GN args: use_goma = false is_debug = true ffmpeg_branding = "Chrome" proprietary_codecs = true enable_nacl = false is_chrome_branded = true is_component_build = true Syncpoint: commit 8ff878076934185e5679df6f75a26f0eff47da22 Date: Thu May 19 11:04:20 2016 -0700 >ninja -C out\Repro mini_installer ninja: Entering directory `out\Repro' [23018/23018] LINK mini_installer.exe >out\Repro\mini_installer.exe No issue. What environment variables do you have set that could influence the build?
,
May 19 2016
Synced again today and the error goes away. I suspect it's just a bad sync. |
|||
►
Sign in to add a comment |
|||
Comment 1 by robliao@chromium.org
, May 19 2016