On Thu, Aug 16, 2018 at 7:48 AM Dan Pike <danny.p...@gmail.com> wrote:
> I think that would be rather difficult, since such a person would need > some level of control over the project, including access to those people > who know how to do it in the first place. Which is a self-referencing > problem, is it not? :) > My suggestion was to *become* those people (as opposed to assuming that they already exist). > May I ask why you choose to depend on obfuscating custom tools such as > depot_tools and those python scripts? If you were to use more standard > stuff, like CMake and plain-old-git commands (or even MSBuild), then it > might be feasible for us to work out what is going wrong and give you some > advice. > Because we want to support our project's needs in a way that's as convenient and as fast as possible. We have requirements (e.g.: pulling in third-party dependencies at specified versions, multiple supported platforms, cross-compilation, a massive codebase with many build-time configuration options) that are somewhat cumbersome to handle with "plain old" commands. Convenience wrappers and sane defaults are the solution. And our build *is* very convenient; it just so happens to be not as well tested on Windows because so few people use Windows for development. But that's where you can help, if you're interested! What is so special about a Windows build of V8 that it cannot be built with > a “normal” project/solution file? Although the GUI side of Visual Studio > drives me crazy with some of its weird behaviour, it is a very powerful > build environment and the Microsoft compiler continues to be pretty stable > and well-documented. > To the extent possible, we want the build system to be the same on all platforms. The more divergence there is, the more effort has to be spent on the build system, and the more platform-specific issues will creep in. If V8 were Windows-only, we would probably just use Visual Studio project files as build configuration; and in fact, as far as I know that was the case in Chrome's very early days in 2008. But these days we also officially support Linux, MacOS, ChromeOS, and Android, and various folks have a strong interest in building for various other operating systems as well (which is not officially supported but can be made to work). If any one of you from the community who wants to develop V8 on Windows > would volunteer to contribute and maintain well-tested instructions, that > would certainly be appreciated by the rest of the community :-) > > > > On Thu, Aug 16, 2018 at 12:09 AM dan Med <litokis.ta...@gmail.com> wrote: > > Yeah that’s what i was trying to say > > > > On Wed, 15 Aug 2018 at 21:55, Mike Moening <mike.moen...@rtssigns.com> > wrote: > > Well said Dan! > > It’s a mess. > > > > Mike M > > *From:* v8-dev@googlegroups.com [mailto:v8-dev@googlegroups.com] *On > Behalf Of *danny.p...@gmail.com > *Sent:* Wednesday, August 15, 2018 1:39 PM > *To:* v8-dev > *Subject:* Re: [v8-dev] Build v8 > > > > For what it's worth, I spent several days a month or two ago trying to get > V8 to build on Windows and eventually gave up (I was hoping to step through > the source to work something out). > > Your Windows documentation definitely could do with someone actually > trying it from scratch on a clean machine, and documenting exactly what > they did without any jargon/acronyms. The existing documentation gives the > impression that it is a Linux-script with a few comments added for Windows > by people "guessing" what they think they might have "tweaked" on their PC > to make it work. > > Things like this step: > > 5. tools/dev/v8gen.py x64.release > > tells me that you are assuming that I am a python developer and have set > up the file associations accordingly. I am not, so Windows merely prompts > me to ask how I want to open the file "tools\dev\v8gen.py". > > I do have several instances of python.exe on my machine (one of them is > yours). Do you want me to run the python.bat file, here? The contents of > that file look a bit weird to me. It looks like it's trying to find a file > called "%~dp0python_bin_reldir.txt" (yes, there's only one '%' in there). > This, with my admittedly limited understanding of Windows batch command > syntax, seems to be gibberish. Who is ~dp0? That's a Unix home folder, not > a Windows one, surely? > > I'll stop there; hopefully you get the point that you need to write some > Windows documentation. Please don't try to "improve" what you have, just > get someone who understands Windows and has a clean machine to write one > from scratch! > > > > Thanks :) > > > > Dan > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to a topic in the > Google Groups "v8-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/v8-dev/ieqbMbmW3DE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
