I am new to xslt and we are using currently version 1.0, now we have to upgrade to version 3.0
what are the steps i have to follow? Is there any processor i need to replace or just all the xsl files will have new version like
<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
Related
What are the minimum compute capability requirements for:
CUDA 5.5?
CUDA 6.0?
CUDA 6.5?
CUDA VERSION Min CC Deprecated CC Default CC Max CC
5.5 (and prior) 1.0 N/A 1.0
6.0 1.0 1.0 1.0
6.5 1.1 1.x 2.0
7.x 2.0 N/A 2.0
8.0 2.0 2.x 2.0 6.2
9.x 3.0 N/A 3.0 7.0
10.x 3.0 N/A 3.0 7.5 (3.0 deprecated in 10.2)
11.x 3.5 3.x 5.2 8.6 (11.0:8.0, 11.1:8.6, 11.8:9.0)
(CUDA 11.5 still "supports" cc3.5 devices; the R495 driver in CUDA 11.5 installer does not)
12.0 5.0 N/A 5.2 9.0
Min CC = minimum compute capability that can be specified to nvcc (for that toolkit version)
Deprecated CC = If you specify this CC, you will get a deprecation message, but compile should still proceed.
Default CC = The architecture that will be targetted if no -arch or -gencode switches are used
Max CC = The highest compute capability you can specify on the compile command line via arch switches (compute_XY, sm_XY)
Actually for CUDA 10.0:
with Tensorflow: The minimum required Cuda capability is 3.5.
with Pytorch: Found GPU0 GeForce GTX 650 which is of cuda capability 3.0.
PyTorch no longer supports this GPU because it is too old.
I have been searching the internet to find the version of MPI in the Microsoft's MSMPI v9.0.1.
Is it MPICH1 (1.0, 1.1, 1.2 etc) or MPICH2 (2.1, 2.2) ? Does anybody know the full version number?
Thanks!
Is it possible to configure DPI Awareness value using cmake or some script?
Create a manifest file (.manifest is important) with the following content:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<asmv3:application>
<asmv3:windowsSettings>
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
see https://learn.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dpi-awareness-for-a-process
Then add it to your binary target in CMake using:
target_sources(your-binary PRIVATE path-to-the-file-above.manifest)
You'll need CMake 3.4 or newer, see https://cmake.org/cmake/help/v3.4/release/3.4.html#other
There is no internal manifest support in CMake, but you can use it, there are couple of hints on this site (e.g. people using manifest e.g. because of UAC etc.).
About DPI, search other topic on SO e.g. here
I found this helpful. Applying manifest using cmake.
https://gist.github.com/bjornblissing/6fc452fe7ec1fdfe3419
Background
We have dependencies to several Xalan and Xerces versions in our rather large C++ system. This has accumulated over the years, and is not optimal for several reasons.
Now we're migrating from Solaris to Linux, and we think it makes sense to consolidate third party dependencies to a minimum.
We've determined that we still need Xerces 2.8 and Xerces 3.x. And Xalan 1.x
Target platform is RHEL6.
Problem
From RHEL repo we can get Xerces 3.0 and Xalan 1.10 (build against Xerces 3.0)
We've installed Xerces 2.8, under /usr/local...
We can't figure out how Xalan is supposed to work with Xerces (link wise). That is:
Do we need two Xalan libraries, one linked against 3.x and one against 2.8?
Can we have one Xalan version, let's say 1.11, that (by some magic) works with both the xerces versions?
We can't be the only one with this problem, or are we just idiots? (which would be the best scenario... :))
From what I've just read at xerces.apache.org , Xerces 2.X and Xerces 3.x have different API's and therefore you'll need to link with one OR the other.
And as you can see from xalan.apache.org:
"The Xalan-C/C++ 1.11 library requires the Xerces-C/C++ XML Parser 3.0 or newer, version 3.1.1 is preferred.", while Xalan 1.10 requires Xerces 2.7.0 (will probably work with 2.8.0).
So yes, you will need two different versions of Xalan libraries, unless you can resolve your dependencies to Xalan 1.11.0 only, in which case you can have only one installed Xalan and one Xerces.
Probably most of all problems of xerces + xalan are because of xerces definition of XML character "XMLCh" in Xerces_autoconf_config.hpp (generated header). I have been trying to build on windows xerces 3.2.2 and xalan 1.11, and faced types missmaching...
E.g., DirectoryEnumerator.hpp, struct FindFileStruct, has function:
const XalanDOMChar* getName() const
{
return name;
}
name is "wchar_t name[260];" from corecrt_wio.h, struct _wfinddata64i32_t (it is Windows part...).
XalanDOMChar is typedef of "XMLCh".
For some reason xerces 3.1.1 generates XMLCh as "wchar_t", but xerces 3.2.2 - as "char16_t". And xalan has some code that is oriented on "wchar_t"...
What is the XSL version supported by Xalan 1.8 library ?
The XSLT version that is supported by all versions of Xalan is XSLT 1.0.
What is the XSL version supported by Xalan 1.8 library ?
1.0
Just in case it changes in the future: generally, you can ask any XSLT processor to report on the version it supports with:
<xsl:value-of select="system-property('xsl:version')" />