12-01-2022, 02:31 PM
OK, after some time going over the solutions. There is no solution. I did find the program I forgot about. The problem being it's for patching a single file.
Here is the real problem. Any release of QB64 involves 1000's of Full release files. Actually unless something major happens, only a dozen or 100 files change from the previous release. Some get removed/changed/added. There must be a way to use some of the "free" code release programs. I am all for a smaller quicker program update way. If it's easier to update end users are more inclined to do so.
Programming is now a hobby for me, but once I did it for work. I kept current, so I know there are professional tools to control code releases. Somewhere a free version of these tools could be used by the QB64 development community. How hard could it be to compare release-A to new release-B. Come up with a release modification file C ?
Anybody knows of or use's something like this ?
Why bother? I am all for getting more users on board the QB64 train.
Here is the real problem. Any release of QB64 involves 1000's of Full release files. Actually unless something major happens, only a dozen or 100 files change from the previous release. Some get removed/changed/added. There must be a way to use some of the "free" code release programs. I am all for a smaller quicker program update way. If it's easier to update end users are more inclined to do so.
Programming is now a hobby for me, but once I did it for work. I kept current, so I know there are professional tools to control code releases. Somewhere a free version of these tools could be used by the QB64 development community. How hard could it be to compare release-A to new release-B. Come up with a release modification file C ?
Anybody knows of or use's something like this ?
Why bother? I am all for getting more users on board the QB64 train.