Quote:
Originally Posted by jackie_w
@geek1011,
I do have a question. Am I right in thinking that preparing a patch for a nickel nozlib CSS stream is exactly the same as preparing a patch for one of the other 3 files? i.e. it's essential for find/replace string lengths to be maintained at all times.
All we need now is another new firmware so we can fully test the theory that it should be easier to prepare/apply patches in future  |
Yes, maintaining string length is required for nozlib patches. In the future (maybe in a few months), I will probably implement css-specific functions to allow patching CSS without even bothering with string replacements or finding the correct stream (I might have mentioned the details somewhere above).
As for the new firmware, I also hope it comes soon, as I'm on vacation later this summer and I want to be able to be there when the new firmware comes out. GeoffR finally responded to my PM, and I've told him everything needed to release a new version, so it should work out fine even if I'm not available. Basically, you just make a new dir for the new firmware, you comment out the outdated patches, you update the ones you can, you check the build status, then you create a GitHub release. The zips are automatically generated and tested.