Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: info@gardinal.net
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] PRIx64 and msvc
Date: Wed, 08 Mar 2023 09:54:18 -0700
Message-ID: <4821c114081c89fd262f5caefdaaaa69@gardinal.net> (raw)
In-Reply-To: <CA+anqdzgeKrP0yFDC6AvB8cYeznpCjf=0cu3=f8A_a-1E2_9wQ@mail.gmail.com>

Le 2023-03-08 09:38, Hendrik Leppkes a écrit :
> On Wed, Mar 8, 2023 at 5:34 PM <info@gardinal.net> wrote:
>> 
>> Le 2023-03-08 09:10, Hendrik Leppkes a écrit :
>> > On Wed, Mar 8, 2023 at 4:02 PM <info@gardinal.net> wrote:
>> >>
>> >> I'm compiling with msvc and get some errors with PRIx64 and similars.
>> >> For example:
>> >> snprintf(name, sizeof(name), "0x%"PRIx64, ch_layout);
>> >>
>> >> won't compile, but this work (with the extra space):
>> >> snprintf(name, sizeof(name), "0x%" PRIx64, ch_layout);
>> >>
>> >> Can this be included in the sources without introducing problems for
>> >> other platforms?
>> >
>> > You'll have to provide more information. We have automated builds with
>> > MSVC which are running just fine right now.
>> >
>> > - Hendrik
>> > _______________________________________________
>> > 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".
>> 
>> For example, in ffplay.c sample (ffmpeg version 5.0.2):
>> 
>> if (is->audio_filter_src.channel_layout)
>>          snprintf(asrc_args + ret, sizeof(asrc_args) - ret,
>>                   ":channel_layout=0x%"PRIx64,
>> is->audio_filter_src.channel_layout);
>> 
>> gives the following error:
>> error C3688: invalid literal suffix 'PRIx64'; literal operator or
>> literal operator template 'operator ""PRIx64' not found
>> 
>> The error is gone when adding a space before PRIx64.
>> 
>> Note that I'm mixing C and C++ in my projet. Compiling in plain C 
>> seems
>> to work.
> 
> This is C code, it has to be compiled as C. You can set this for every
> individual file in MSVC if you have to.
> 
> We cannot support modifications or custom projects, of course.
> 
> - Hendrik
> _______________________________________________
> 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".


Alright, thanks for the quick response.

Every time I update ffmpeg, I have to manually add those spaces. I was 
thinking that I may not be the only one in this situation and that 
adding these spaces in the sources could help other people.

Best regards,
- Gardinal
_______________________________________________
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".

      reply	other threads:[~2023-03-08 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 15:01 info
2023-03-08 16:10 ` Hendrik Leppkes
2023-03-08 16:33   ` info
2023-03-08 16:38     ` Hendrik Leppkes
2023-03-08 16:54       ` info [this message]

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=4821c114081c89fd262f5caefdaaaa69@gardinal.net \
    --to=info@gardinal.net \
    --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