Custom Query (202 matches)
Results (34 - 36 of 202)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #76 | fixed | Short path name in COBIA_INCLUDE environment variable during installation | jasper | jasper |
| Description |
In trying to debug the issue reported here: http://www.cape-open-forum.org/viewtopic.php?t=725&p=2563#p2563 on my own file system I found that the directory I created for the test does not actually have a short equivalent, which according to the documentation of GetShortPathName? is a valid outcome of the function call: https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getshortpathnamew This means that the current custom action by the installer will attempt to make a short path name (which in case of the above forum item apparently succeeded, the issue there is another one), and sometimes this will result in a long path name nevertheless. We could leave as is, and accept that sometimes the path name contains spaces, or remove the attempt to make a short path name altogether, which means the long path name (which will always contain spaces, given the default installation folder) will be used. Comments? |
|||
| #77 | fixed | improper CAPE version in examples | jasper | jasper |
| Description |
Examples incorrectly register as CapeVersion? = 1.1, fixed to 1.2; note that the use of this item is limited now that the CAPE-OPEN component cat-id is version dependent and components can implement more than one CAPE-OPEN version. |
|||
| #79 | fixed | Installer should use new type libraries | jasper | jasper |
| Description |
New type libary installers should be used in COBIA installers |
|||