When I use ractive, I saw some versions, but I don't know what is the difference between ractive.runtime.js version and ractive.js version.
So who can tell me?
The runtime version doesn't include the template parser. That means your templates have to be precompiled in a build step. If in doubt, use the non-runtime version.
Related
I have two version of buildroot downloaded. Older version (2014.05) of buildroot needs qtbase-opensource-src-5.2.1. It's OK because the source for this version of Qt has already been downloaded.
But I want to use second version of buildroot (2015.08) for some reason. However, second version needs qtbase-opensource-src-5.5.0. Unfortunately, the computer I use, is not able to download something from internet. So I want to use Qt 5.2.1 with the newer version (2015.08) of buildroot. I cannot figure out how to tell buildroot to use this version of Qt. In menuconfig, I cannot change the version. I cannot find a config or similar file to configure the version of Qt.
Buildroot does not support choosing a specific version of a package, because very often the way to build it will be different for a different version. For Qt5, this is certainly the case.
In your particular case, the easiest is probably to just remove package/qt5 from the buildroot tree, and replace it with a copy of package/qt5 from the 2014.05. Note that this will only work correctly if you use no package that depends on Qt. Also, there may be some changes needed to make it work in Buildroot 2015.08. For example, BR2_PREFER_STATIC_LIB has been renamed to BR2_STATIC_LIBS.
Maybe, however, it's easier to just put qtbase-opensource-src-5.5.0 on a flash drive :-)
I have been trying to execute R code on U-SQL using the R extensions mentioned in the documentation (https://learn.microsoft.com/en-us/azure/data-lake-analytics/data-lake-analytics-u-sql-r-extensions).
When I try to execute the example scripts mentioned in the link above, it throws the error:
C# error CS1739: The best overload for 'Reducer' does not have a parameter named 'rReturnType'
And when I remove the rReturnType parameter I am unable to make sense of the output.
Are there any other Extension.R parameters which will serve the same purpose?
Which version of the extensions have you installed? if you installed them some while ago, the parameters of the libraries may have changed and be out of date with the documentation. I am pinging the owner of the documentation page to make sure that the docs are in sync with the latest released version.
UPDATE: I checked and the documentation is aligned with the latest version. Please go to the ADLA Portal and reinstall the U-SQL Extensions. Please make sure that you read up on the release notes in case you or someone else uses the older version.
I am working with different cross compiler compilers, and an evaluation of premake for GCC has proven to be very successful.
Now i want to use Premake for cross compiling to different embedded targets and compilers. Is there someone that knows how to extend premake with new compilers, or it is possible already with current functionality in Premake5
If you haven't already, get the latest source code from the GitHub project. Take a look at the existing toolset adapters in src/tools. Read through the "Extending Premake" section of the project documentation. Ask questions on the Premake Developer forums.
I recently downloaded a new symfony2 package for websockets and included it into my composer file,
when I called
php composer.phar update
It automatically updated my Symfony version and I was wondering if updating Symfony2 will break the website in the long run, since part of my source code could become obsolete (deprecated)
Yes, if composer downloads a version of a dependency that's not backward compatible with the version that you used to develop your website, things might/will break.
However, you can limit the possibility by defining good rules in your composer.json.
First of all, it might be good to learn about semantic versioning if you haven't heard of it already. Many projects are following the rules of semantic versioning, which basically state that if a project/library has changed in a way that is not compatible with earlier versions, it's main version number should be incremented. For instance, if 1.5.x had a certain feature, and an update is made where that feature is changed or no longer available, the new version number should be 2.0.x instead of 1.6.x.
Knowing this, you can use Composer's tilde operator (~) to define useful version constraints. For instance, to add the dependency to symfony's files, you can add the following requirement to your composer.json:
"symfony/symfony": "~2.3"
which is equivalent to:
"symfony/symfony": ">=2.3,<3.0"
or, in plain English: 'give me a version of symfony/symfony, at least version 2.3 or higher, but lower than 3.0'. If Symfony follows semantic versioning correctly, no backward incompatible changes should be made in any 2.x versions (and, if any backward incompatible changes are made, they should come with version 3.0), so you should be fine.
This actually depends on how your composer.json is configured. If your dependencies use SemVer, and you are referencing them in your composer.json only allowing patch version changes (like "package-name": "1.1.x"), then everything should usually be fine.
Also, note that you can pass a package name as a parameter to the composer update command, e.g. php composer.phar update <vendor/dependency-name>. This will tell Composer to only check if there are updates available to <dependency-name> package, given your current composer.json version constraints.
If you want to check that nothing is broken after an update and you're not keeping the update scope as narrow as I specified, then something could break. The best way to detect and avoid this is by testing.
You should read about composer.lock file. This will make sure that Composer will not update any version of the repository and only what you specify in the lock file
I'm having a problem with adding the Qxt library to Qt Designer. The error it gives is:
Cannot load library C:/Qt/4.6.2/plugins/designer/QxtDesignerPlugins.dll; The specified module cannot be found.
Any ideas on what the problem is?
Try setting the QT_DEBUG_PLUGINS environment variable to 1 and then try again. This should give you some additional debug output that will help isolate the problem.
Did you check that this file is actually there?
Usually, the problem with designer plugins is that they're installed in the wrong directory, or linked against a different Qt (esp. debug vs. release).
Check that the plugin itself can find all the dlls it depends on. Use depends.exe (Dependency Checker) or maybe FileMon.exe to find out.
The error message can be a bit misleading, as it is the same if any of the primary dlls dependencies are missing too.