Custom Query (202 matches)
Results (22 - 24 of 202)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#26 | fixed | Arrangements of sections in main page | jasper | michelpons |
Description |
The section on COBIA-COM interoperability mentions component registration while the section on CAPE-OPEN registry comes much further down. Two options here: move the section on CAPE-OPEN registry before the section on COBIA-COM interoperability while keeping the section on COMBIA where it is now or move down the section on COMBIA, below where the section on the CAPE-OPEN registry is. This main page begins as high level stuff then dives in details such as basic data types before going back to middle level stuff (implementing PMCs). I don't think the sequence is easy to follow. |
|||
#27 | fixed | CapeInterfaceAdapters.h not carrying copyright and terms notices | jasper | michelpons |
Description |
Seems that:
is missing from CapeInterfaceAdapters?.h. |
|||
#29 | fixed | Environment variable SIGNTOOL in Readme | jasper | michelpons |
Description |
The Readme file developed for explaining building of COBIA related installers starts with instructions about environment variables. (Temporary) Instructions for new release, Jasper 2020: 2 3 ENVIRONMENT 4 - Set the environment variable SIGNTOOL to point to Signtoo.exe (Win 10 SDK) Should this be a system-wide environment variable or a user environment variable? Secondly signtool.exe (missing the "l" above in the readme file) exists at two locations at least: C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64, and another one under C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86. If the environment variable is created to point to a location, which one should be used? |