Open GoogleCodeExporter opened 9 years ago
Possible todo:
- expect to have DCC executable in "./" directory of Installer that uses nsisdbg plugin.
- get list of used plugins from installer to nsisdbg plugin list struvcture.
- pass the structure ( in CMD formatting ) to external DCC to generate map files ( compile-time of installer )
- create "Enable Plugin code coverage" and button "view coverage results <the otuput format" passed to DCC cmd.
Original comment by linards....@gmail.com
on 2 Nov 2012 at 11:21
Currently crystalized issues:
1. Plugoins can toeretically be written in any language supporting WinAPI ,
POSIX and cdecl / pascal callign convetions.
It results in following issues:
2. there is no solid way to provide .map files for each plugin.
3. if there is .map file, it must be comaptible with DCC code-base parser.
4. if we reomve MUST part, the plugin itself should siganlize to nsisdbg about
the language it is written in.
5. that would allow the nsisdbg tool to distingish and make call to
appropritate Code coverage tool ...
...
Anyone willing to contribute? :)
Original comment by linards....@gmail.com
on 28 Nov 2012 at 11:44
Original issue reported on code.google.com by
linards....@gmail.com
on 24 Sep 2012 at 8:59