For some days I've been looking forward to build QtWebkit with V8 support.
I found lot of resources over the internet, some of them old like this one from 2010:
http://webkit.sed.hu/blog/20101216/benchmarking-qtwebkit-v8-linux
"For some time it has been possible to build and run QtWebKit on Linux
using Google's V8 JavaScript engine instead of the default
JavaScriptCore."
And this one from 2011:
https://lists.webkit.org/pipermail/webkit-qt/2011-January/001111.html
The current trunk should also build now with:
Tools/Scripts/build-webkit --qt --v8
I also found this one:
http://qt-project.org/wiki/V8_Port
THE PROJECT WAS ABANDONED [bugreports.qt-project.org]
The --v8 doesn't seems to be recognized in Webkit's build_webkit script and there doesn't seems to be a similar option.
A find in Webkit's source revealed v8 tests and bindings existing in the project.
So it's there a way to build QtWebkit with v8 or is it abandoned?
People at #qtwebkit (freenode.net) said that V8 support was abandoned.
But I found this that may be worth trying:
https://github.com/qtwebkit-v8ers/qtwebkit-v8
Related
trying to build documentation for a project.
the project uses the doxygen product which rpm contains the /usr/bin/docsetutil binary? Doxygen 1.8.4 generated output Makefile is looking for it...
thx.
That binary is part of the OS X / macOS developer toolchain. On my OS X 10.9.5 system, it exists at /Applications/Xcode.app/Contents/Developer/usr/bin/docsetutil.
I don't know of a workaround for other platforms, so you'll probably want to have a Makefile or a separate Doxyfile or something that just doesn't attempt to build the docset unless you're on an OS X system. And just build the docsets on a Mac, if you have access to one.
It will be interesting to see if a Free replacement docsetutil for GNU/Linux ever pops up, now that the Dash developer has opened the door for offline documentation browsers on other platforms to use his docsets (e.g., Zeal). As far as I know (and I don't know much), the Dash web site at kapeli.com is acting as the central repository at the moment.
ref: I had the same question, and discovered the answer in this otherwise unrelated bug report for the TYPO3 CMS. I'm leaving this answer here for other folks who find this by way of a search engine.
I am working with erlang project which uses google protobuf via https://github.com/basho/erlang_protobuffs
After some time I've got not such good impresion about it (I've found usage of this technology in erlang very clumsy and inconvenient). But of course, I known that this is because I can not cook it properly.
Which open source erlang project are using erlang_protobuffs? I am interested in best (or at least sufficient) practices of its usage.
I assume that you mean http://github.com/basho/erlang_protobuffs library.
From major opensource projects I know only basho's riak using this library, although
Github code search gives a lot of different projects.
Note, that this library is not only one, take a look at this post
My standard route has been to go to confluence, find the docs sections, then navigate through to the install docs for the version, e.g. sakai 10:
https://confluence.sakaiproject.org/x/iYGLBQ
Through one means or another I happened across the source route to this too, so starting here....
http://source.sakaiproject.org/release/
You get redirected to the latest stuff, and appended version numbers to that url gives you other docs, e.g. adding 2.8.2 or 10 to the end of the url
But the links to what I should download are quite often not there, at the time of writing the 10 tar ball and zip in the confluence links are dead and the source.sakaiproject links doesn't have the 10 docs yet (redirects to 2.9.3) presumably this is because v10 is not released yet....
So, I'd like to evaluate a new version of a sakai source install, what's the best way to do this? (considering the official documentation for install is still being formed)
Do I download the latest SVN, or the latest RC or the latest beta or??? How do I know what's best to test against without being "too" bleeding edge? Is there a recommended tar ball/zip link to test against? Is there a "latest good" SVN branch?
The latest code is always in the Sakai trunk (currently svn):
https://source.sakaiproject.org/svn/sakai/trunk/
That code may very well not be stable though as it is where things are being actively developed. If you are not actively developing then you should stick to the releases as indicated on the project website here:
http://sakaiproject.org/current-release
If you want to use something in between (say an upcoming release) then you can grab the most recent tag or maybe use a recent branch (both currently in svn, latest shown below at the time I write this):
https://source.sakaiproject.org/svn/sakai/branches/sakai-10.x/
https://source.sakaiproject.org/svn/sakai/tags/sakai-10-rc02/
The reality of the situation is that if you want to use something other than the release then you should really participate in the dev community for Sakai. Joining the mailing lists and the weekly calls will provide the information you are asking about and much more.
Some questions about Simple.Data and Mono:
Can I safely choose Simple.Data for a new project using Mono today?
There is the intention to maintain Mono compatibility in future versions?
The features are the same as the version for Windows?
Some testimony from someone who has already used in Mono?
Many thanks!
There will be a new official Mono build soon as part of the RC process. For now you should be able to clone the GitHub repo (http://github.com/markrendle/Simple.Data) and build the latest version.
Mono support is a requirement of the project, and will continue in all future versions.
Everything that works on Windows and MS.NET should work on Mono on OSX and Linux. If you find that something does not work, that is a bug and should be reported at http://github.com/markrendle/Simple.Data/Issues .
I have not personally got any projects using Simple.Data on Mono, so I can't offer a real testimony, but there are ~700 tests which all pass using Mono 2.10 on Mac OSX against a SQL Server DB.
Hopefully this is a silly question and there's really a simple solution somewhere out there but...
Has anybody successfully gotten DbLinq to play nicely with Mono 2.4 on Mac OS X 10.5?
I've got my SQLite database ready but for the life of me, I can't find sqlmetal to generate my objects.
I'm guessing I might have to download a previous version of Mono that included sqlmetal, build and install it, and then just use the code generated from that version on Mono 2.4...but I'm hoping to avoid it at all costs.
I'd avoid using DBLinq for production code... many of Linq-To-SQL's features aren't implemented, and walking through the source code shows a low level of maturity... many of the methods are not implemented or marked as "unterminated".
...you've been warned!
Using the pre-compiled binary in this case just doesn't work.
To get a properly generated DbLinq data layer, you have to use the sqlmetal tool included with Mono (but, apparently, not with the pre-compiled binaries for OS X). You have to pull down the Mono trunk (along with all the dependencies) and build Mono from the source.
Once you build and install Mono from source, you should have the sqlmetal tool. Once you generate your code, it's as easy as including the generated *.cs file and importing Mono.Data.Sqlite.
Mono 2.6 will include for the first time a preview of DbLinq with Mono. You can take it out for a spin today if you install DbLinq on your own side-by-side with your current Mono setup.