Yes, headers could be modified using a script. I'd build the list by first pattern matching all function declarations in header files, then remove all unwanted functions, then use this list as the tizen api whitelist. The list would include the header file name and function signature tuple.
To modify header files, I'd use this whitelist, with a script, so the task could be automated whenever header files are updated. Just a thought. Thanks, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Carsten Haitzler <[email protected]> Sent: 09/11/2015 10:48:24 am To: Peter <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [Dev] Tizen api On Mon, 09 Nov 2015 09:09:48 +1000 (AEST) Peter <[email protected]> wrote: > Any thoughts on using a macro to identify Tizen native api for > developers? > > Presently developer's have to submit an application to the store to > determine if the api used by their application is acceptable. > > Regards, > > Peter. > Sent from my Samsung device. that's a LOT of headers to modify. what is probably best is if there simply is a verification tool that runs on a binary that tells you what is "invalid". it's a shame that it isnt a standard part of sdk build process etc. by now. :(
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
