2008/10/9 <[EMAIL PROTECTED]>: > The other approach is to specify the full path to the build > directory's libv8.so in your g+ link line, but that's a dreadful hack, > and quick test programs linked that way should never be deployed.
I don't mean to be picking on you at every possible instance, but this is not a "dreadful hack" at all. This is how most of us do it, because it avoids polluting our systems with development libraries that will likely be replaced by distribution binaries at some point anyway. It is not easier to maintain a manual copy of the V8 libraries and headers in /usr/local, and you should only install it there if this is more convenient for you (i.e., if you use V8 in multiple projects, and want them all to stay up-to-date, and if you want each project to assume that every system it will be deployed on has a pre-installed V8 library). This is a perfectly valid and standard way of dealing with this: g++ -o your_target -I/path/to/v8 your_source_file.cpp /path/to/v8/libv8.a Many projects include V8 in their own build systems, so it would be distributed along with the project source, in order to tackle dependency problems, asynchronous versions, and general installation hassle. - Simon --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
