My Chromium don't support xp

[杜士雄]

My compile setting:

set GYP_GENERATORS=ninja,msvs-ninja

set GYP_DEFINES=component=shared_library

set GYP_MSVS_VERSION=2013

Chromium Debug

Version:

MAJOR=48

MINOR=0

BUILD=2564

PATCH=103

And i copy the package to xp ,and it failed to run,why?

[PhistucK]

Note that "failed" is not enough information. What do you see? Do you have a stack trace? A log? An error message? Anything?

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[Ramesh Srigiriraju]

Dusx,

Visual Studio 2013 has some compatibility issues with Windows XP.  Specifically, the remote debugging and profiling tools are not available:

https://www.visualstudio.com/en-us/products/visual-studio-2013-compatibility-vs.aspx

[杜士雄]

how should i set this in chromium

在 2016年2月29日星期一 UTC+8上午9:43:58，TTCUSM写道：

[杜士雄]

how should i set this in chromium

在 2016年3月4日星期五 UTC+8上午10:38:11，杜士雄写道：

[杜士雄]

[Ramesh Srigiriraju]

Dusx,

Are there any other versions of Visual Studio on your Windows XP machine?

Maybe you can change your Platform Toolset to something that is compatible.

[杜士雄]

where should i set the tool set, vs or gyp?

在 2016年3月4日星期五 UTC+8下午10:52:52，TTCUSM写道：

[杜士雄]

I made a test, change it in vs to xp_120,and run gclient runhooks, the toolset was reset,then how shuold i do

在 2016年3月5日星期六 UTC+8下午4:26:36，杜士雄写道：

[Ramesh Srigiriraju]

Try setting it in gyp.

[杜士雄]

I searched the "toolset" & "v120_xp" in the src path , but did not found the content about it, could you please tell in which gyp file, and how

在 2016年3月5日星期六 UTC+8下午5:57:45，TTCUSM写道：

[杜士雄]

The set command support macros, there is no one about toolset

在 2016年3月5日星期六 UTC+8下午8:03:40，杜士雄写道：

[Bruce Dawson]

Trying to change the toolset used to build Chromium on Windows is a huge undertaking and will ultimately fail because the Chromium team is moving in another direction (towards VS 2015). And, the toolset may be the wrong thing to change anyway.

Until recently Chromium was designed to run on XP. I'm not sure whether any XP incompatible changes have been committed yet, but I wouldn't be surprised. The safest thing would be to sync to a point about six weeks ago when XP was still supported.

But, that is for the question of targeting XP. If you are trying to build on XP then you may hit other issues. For instance, most XP installs are 32-bit, and Chromium cannot build on a 32-bit OS.

These concerns:

> Visual Studio 2013 has some compatibility issues with Windows XP.  Specifically, the remote debugging and profiling tools are not available

are also not related to building or running Chromium on XP. Debugging and profiling are only necessary after you have successfully created a built that will run.

Once Chromium changes the default toolset to VS 2015 then building on XP will not be possible. VS 2015 requires Windows 7 or higher in order to compile code.

So... if you want to build on XP then make sure you have 64-bit XP, and understand that you will not be able to keep syncing because VS 2015 will soon be required.

If you want to run on XP then make sure you sync to a point prior to when the first XP-incompatible change got committed, which is probably sometime in the last six weeks.

[杜士雄]

I downloaded mini_installer with version 48 and 50,tested it on xp,the 48 succeded, but 50 failed

My woring version is 48.xxx.xxx.103, my 48 test version is 48.xxx.xxx.116, and can i deduction that my woring version is still supported for xp?

在 2016年3月6日星期日 UTC+8上午2:25:51，Bruce Dawson写道：

[Bruce Dawson]

http://chrome.blogspot.com/2015/11/updates-to-chrome-platform-support.html

Version 49 should also work on XP, I believe.

[杜士雄]

OK,Tks

在 2016年3月8日星期二 UTC+8上午2:57:11，Bruce Dawson写道：

[lion]

Hi, have you ever solved the problem?

Now I encounted the same problem to you

在 2016年2月23日星期二 UTC+8下午8:05:35，杜士雄写道：