Closed DhruvGandhi31 closed 1 year ago
Please don't send pull requests that don't work - if it doesn't even compile it's not ready.
I am working on resolving the issues after migrating the gpac code from 1.0.1 to 2.2.0. I see there are a lot modifications required, I have already spent hours on it. I was wondering after I modify the code, if the build compiles and the ccextractor cli shows no quirks, should I consider the job as done?
I am working on resolving the issues after migrating the gpac code from 1.0.1 to 2.2.0. I see there are a lot modifications required, I have already spent hours on it. I was wondering after I modify the code, if the build compiles and the ccextractor cli shows no quirks, should I consider the job as done?
If it breaks things, no.
The job is to update GPAC 1 to 2, not to break what we have and leave us with garbage.
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
GPAC version is updated to 2.2.0 I have made changes only in gpacmp4 (ccextractor/src/thirdparty/gpacmp4/) library. Some changes are minor like 'GF_INSERT' is replaced by 'GF_ADD' and some changes are major like adding new method or replacing existing code snippet as a whole. Please note that these changes may reflect on other libraries and other part of code which uses gpac. The changes that I have made are in accordance with the official GPAC repository.