Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] bsf: use standard include paths
Date: Wed, 10 Apr 2024 16:11:45 +0200
Message-ID: <AS8P250MB074494704C2B246B486366F98F062@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20240409211334.138302-1-andrew@ziglang.org>

Andrew Kelley:
> Removes the special -I flag specified in the avcodec/bsf/ subdirectory.
> 
> This makes code copy-pastable to other parts of the ffmpeg codebase, as
> well as simplifying the build script.

If you want to make the code copy-pastable to other parts, you need to
disallow using the ordinary relative-path header inclusion. And I don't
see a simplification of the Makefile.

> 
> It also reduces ambiguity, since there are many instances of same-named
> header files existing in both libavformat/ and libavcodec/
> subdirectories.

What ambiguity? As said above, said ambiguity emanates from using
inclusions with relative paths (and from using the same header
filenames) and not adding an -I for the parent folder for the files in a
subfolder. (It would be different if we did something nuts like adding
-Ilibavcodec to the compilation of libavformat files).

- Andreas

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2024-04-10 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 21:13 Andrew Kelley
2024-04-10  0:04 ` Lynne
2024-04-10  1:11   ` Andrew Kelley
2024-04-10  1:23     ` James Almer
2024-04-10  4:54       ` Anton Khirnov
2024-04-10 13:47         ` Lynne
2024-04-10 14:11 ` Andreas Rheinhardt [this message]
2024-04-10 18:35   ` Paul B Mahol
2024-04-10 21:06   ` Andrew Kelley
2024-04-10 21:27     ` Andreas Rheinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AS8P250MB074494704C2B246B486366F98F062@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git