Providing Turboactivate.dat as arraySolved

I just realized that I need to ship Turboactivate.dat with my software so that the software can be activated on the customers computer. Am I right? Well, I could take care of this when I would ship an executable. But I develop a library that other software vendors use to create their own software. They have their own build systems and directory structures and I'm afraid having Turboactivate.dat in the right directory would always be a problem. But there is an easy solution: Couldn't we get a function TA_PDetsFromArray(unsigned char* p,size_t length)?

Then one could easily turn the Turboactivate.dat file into an array. Under Linux we have the standard command xxd for that:

$ cat HelloWorld.txt HelloWorld

$ xxd -i HelloWorld.txt unsigned char HelloWorld_txt[] = { 0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x57, 0x6f, 0x72, 0x6c, 0x64, 0x0a};unsigned int HelloWorld_txt_len = 11;

Such a command would solve the problem. But just another idea for the future: It could improve the usability of the licensing product when the Turboactivate.dat download would be replaced by a Turboactivate_dat.cpp file that contains such an array. It would avoid the need to ship the *.dat file and it would avoid errors caused by having it in the wrong directory.

We already have a function for this (for more than 3 years now): TA_PDetsFromByteArray. Look in TurboActivate.h for all function definitions, descriptions, and error codes.

https://wyday.com/limelm/api/ta-changes/