Thanks for your reply Christian. I am happy to build v8 separately.
Will post again when I'm further down the track and have something more than mere observations to contribute. Simon On May 25, 7:48 pm, Christian Plesner Hansen <[email protected]> wrote: > We deliberately don't use anything but the most basic standard c > libraries so there hasn't been any reason for us to avoid using those > names for our own files. > > How do you build your files? If you build v8 separately and use it as > an external library you shouldn't have any problems with v8 source > files on your include path. > > -- Christian > > On Mon, May 25, 2009 at 4:10 AM, skid <[email protected]> wrote: > > > Hi, > > > I'm currently implementing V8 interface in my app in order to compare > > with my current activescript / jscript solution. > > > There may be very good rationale behind it but I have been forced to > > rename v8/src/memory.h to v8/src/v8memory.h. > > > This is because <memory.h> is a popular standard include used to > > commit evil by my code and I suspect others and it seems src/ia32 > > includes require v8/src to be in include path. > > > In future I will attempt to revert to using only string.h in my own > > project for my evil bit banging but was curious if there was perhaps > > some other reason for v8 to be using standard library file names that > > already exist in typical C++ toolchains. --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
