Opened 17 years ago
Closed 4 years ago
#79 closed task (too-old)
ENABLE_HW_CERTIFICATION and DISABLE_STREAM_REUSE
Reported by: | greenemk | Owned by: | martini |
---|---|---|---|
Priority: | normal | Milestone: | Stabilization |
Component: | UNIAUD16 | Version: | 1.1.4RC6 |
Severity: | minor | Keywords: | |
Cc: |
Description (last modified by )
The uni16 build system does not support macros ENABLE_HW_CERTIFICATION and DISABLE_STREAM_REUSE. They are present in the Uniaud16 code to designate sections of code that are uncertain.
The point is to make a decision about whether this code is needed and either fix and enable it, or remove it.
Change History (6)
comment:1 by , 17 years ago
Milestone: | 1.1.4GA → milestone1 |
---|
comment:2 by , 17 years ago
Version: | → 1.1.4RC5 |
---|
comment:3 by , 16 years ago
Description: | modified (diff) |
---|---|
Milestone: | milestone1 → 1.1.4GA |
Severity: | normal → minor |
Summary: | uni16 build system macros → ENABLE_HW_CERTIFICATION and DISABLE_STREAM_REUSE |
Type: | enhancement → task |
Version: | 1.1.4RC5 → 1.1.4RC6 |
I've modified the description to reflect this intent.
comment:4 by , 4 years ago
Hello
I’m giving a hand doing some ticket housekeeping on UniAud.
This ticket is old and referred to an old version of UniAud.
- Please try the latest version 2.2.6. ftp://ftp.netlabs.org/pub/uniaud/Uniaud-20200506.exe
- Or try the latest test release: https://www.os2world.com/forum/index.php/topic,2436.0.html
Please let us know if this same error/suggestion applies to the latest version to update the “version” of the ticket.
If this ticket gets closed because it is too old, remember that you can always reopen the ticket with updated information.
Regards Martin
comment:5 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 4 years ago
Resolution: | → too-old |
---|---|
Status: | assigned → closed |
These are preprocessor macros I added to Uniaud16. The only reason for them was to make it easy to enable or disable them for the process of deciding whether to re-enable that code or remove it.
It had been commented out in such a way as to make it uncertain whether it was done just to test something temporarily or if it really was intended to be removed on purpose. I did not have the understanding or the time to make a determination about it, so I created the macros for the sake of tidiness and easier testing.
It might be more constructive to forget my request to modify the build system for these, and instead change this ticket (or create a new one) to determine definitively whether this code should be uncommented, modified, or removed, and then lose the macros in the process.
It would be ideal to see that in 1.1.4GA.