tor 2024-10-31 klockan 01:08 +0100 skrev Michael Niedermayer: > Hi > > Theres a problem with libavutil, or maybe more than one > > a library implementing a codec that tries do use libavutil and itself > is > used by libavcodec. Creates a (build) dependancy like this > libavutil -> libmycodec -> libavcodec > Thats ok if libavutil is a seperate source but if libavutil and > libavcodec > are in the same source package and are build together
This sounds like you want to avoid having to clone the repo twice. Disk space is cheaper than developer time > , well iam sure > you see this doesnt work > build ffmpeg first, theres no libmycodec, > build libmycodec first, theres no libavutil > now of course this can be worked around by building ffmpeg twice > But this is not documented, not suggested, not tested and not > considered > > of course myself spliting out libpostproc made me realize this issue. > But > its a much broader problem than libpostproc. For libpostproc i can > just > copy everything and remove all libavutil dependancies > And even without that it builds and works fine and all but only > because i had > a prior build libavutil installed from before. Are you trying to make libpostproc into a standalone library in a separate source tree? Why? Surely the build system can be improved to only building it and libavutil if someone wants that /Tomas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
