Comment # 10
on bug 7426
from vadim
Thank you ! I am working on improvements. I think I could get some feedback on
developers maillist also.
I am preparing modifications for makefiles. I will be able to test only linux
host build, I will request some support on developer list to test everything
else.
I will rework Ubiqua and Ember code to exclude extention check. It is even more
difficult to distinguish TI-SmartRF format, because it is only binary blob of
fixed size structures, I will add some analisis based on file content, I will
double check if filesize could be obtained at that point, it is very needed to
know at least size to determine this format.
On Ember-ISD, content of archive will also be tested, I will reuse crc
implementation.
I will double check TI-SmartRF.
On Ubiqua, I will also double check seek positions, because using sequence
nuber of record instead seek offset.
About SQLite and ZZIP. I can do wrappers for usual dinamic linking or runtime
linking(libdl/LoadLibrary), and also there is ability of static linking of
SQLite
I would also prefer to use security key information from ubiqua or ember files.
But it os not very easy to pass it into Edit/Preferences/protocol/ZigBee
NWK/Preconfigured keys.
Am I correct that it is better to use developer mail list to discuss makefiles
and passing data to preferences, to request some build test from other os
users, and then update patch here ?
You are receiving this mail because:
- You are watching all bug changes.