> I have the following approach in mind:
>
> - Code the new stuff in the repo
> - Write a program (with a `main' function) that will eventually
> trigger the "newly added" part somehow.
> - Use GDB to set a break point on the "newly added" part and then
> step through it and confirm whether everything works or not.
> - Repeat
>
> This approach feels slow because for each new modification, the
> library as well as the program that uses it will have to be rebuilt.
> Is this the right approach?
I do exactly this. As Armin mentioned, a batch job for quick calls of
`make' in both the freetype and freetype-demo trees helps a lot.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
