Re: [flac-dev] How to change the dynamic library project name ogg to libogg?

On 06.06.2023 22:33, Martijn van Beurden wrote: Hi, This rabbit hole went quite a bit deeper than I expected. Apparently, CMake prepends 'lib' to library names for unix like environments (including MinGW) but not for Visual Studio. So, when building on Windows, you get either libFLAC.dll and lib

Re: [flac-dev] How to check for 64-bit CPU?

On 30.12.2015 13:57, Thomas Zander wrote: > On 29 December 2015 at 08:08, Erik de Castro Lopo wrote: > >> I would suggest: >> >>#if SIZEOF_VOIDP == 8 > > I believe this is not portable. At least on my machine ("4.2.1 > Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") > it'

Re: [flac-dev] Windows file buffering

On 10.12.2015 19:58, lvqcl wrote: > LRN wrote: > >> The commit mentioned in the feature request should not cause such >> behaviour, as it only does short-lived operations (opens a file, does >> stuff, closes the file immediately after) and is clearly distinguishing >>

Re: [flac-dev] Windows file buffering

On 10.12.2015 10:39, Erik de Castro Lopo wrote: > lvqcl, > > Would you be able to have alook at this one? I think its > Windows related: > > https://sourceforge.net/p/flac/feature-requests/114/ > The commit mentioned in the feature request should not cause such behaviour, as it only does sh

Re: [flac-dev] Apple afconvert & SRC

On 20.07.2015 1:03, Brian Willoughby wrote: >> On Jul 19, 2015, at 2:03 PM, Marcus Johnson wrote: >>> Do you have a source on the CoreAudio quality thing? I'd be very interested >>> in reading more about that. >> >> The following thread seems to touch on all the key words. >> >> http://www.macos

Re: [flac-dev] flac-1.3.1pre1

On 25.11.2014 16:03, Jan Stary wrote: > On Nov 25 00:43:22, mle...@mega-nerd.com wrote: >> Hi all, >> >> As people may have seen there's a pre-release here: >> >> http://downloads.xiph.org/releases/flac/beta/ >> >> Specifically: >> >> flac-1.3.1pre1.tar.xz : The source code >> flac-1.3

Re: [flac-dev] flac-1.3.1pre1

On 25.11.2014 11:43, Erik de Castro Lopo wrote: > > flac-1.3.1pre1.tar.xz : The source code > flac-1.3.1pre1-win.zip : Windows 32 and 64 bit binaries > > Please test. > > I'm particularly interested in hearing about the windows binaries > which were cross compiled from Linux to Windows.

[flac-dev] Building FLAC with LTO

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tried to do this, gcc complained a lot about undefined references. After a bit of mucking with the code, i came up with a few patches. This might be a good conversation starter. The build that i've got out of this does pass the testsuite. To enable L

[flac-dev] ogg_mapping.c

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why is ogg_mapping.c full of variables? Why not macros? - -- O< ascii ribbon - stop html email! - www.asciiribbon.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJTZK5cAAoJEOs4Jb6SI2Cw5dkH/jbXCMBq8hpZzggt7UKImZbc VXc

Re: [flac-dev] Pre-release 1.3.0pre4 (hopefully the last)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2013 13:38, Erik de Castro Lopo wrote: > I have tagged 1.3.0pre4 in git and provided a tarball here: > > http://downloads.xiph.org/releases/flac/beta/flac-1.3.0pre4.tar.xz > > I have built and tested the git tree on: > > linux-x86_64 openbs

[flac-dev] Update ogg.m4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please update m4/ogg.m4 Namely, new version should support --with-ogg=yes or --with-ogg=no (this enables ogg stuff, but does not add -L to OGG_LIBS, that is crucial to keep .pc files clean). ogg.m4 from libogg-1.3.0 will be sufficient. -BEGIN PGP

Re: [flac-dev] flac 1.3.0pre3 pre-release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.04.2013 16:26, LRN wrote: > On 01.04.2013 14:40, Erik de Castro Lopo wrote: >> Hi all, > >> The latest pre-release is here: > >> http://downloads.xiph.org/releases/flac/beta/flac-1.3.0pre3.tar.xz > >> >

Re: [flac-dev] flac 1.3.0pre3 pre-release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.04.2013 16:55, Janne Hyvärinen wrote: > > On 1.4.2013 15:29, LRN wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 01.04.2013 16:24, Janne Hyvärinen wrote: >>> I'm worried about some

Re: [flac-dev] flac 1.3.0pre3 pre-release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.04.2013 16:24, Janne Hyvärinen wrote: > I'm worried about some of the modifications done to the UTF-8 > patch. In commit 2199d086921eb37d249cae0731f334556ec6209d #ifdef > checks were changed from specific FLAC__STRINGS_IN_UTF8 to generic > _WIN32

Re: [flac-dev] flac 1.3.0pre3 pre-release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.04.2013 14:40, Erik de Castro Lopo wrote: > Hi all, > > The latest pre-release is here: > > http://downloads.xiph.org/releases/flac/beta/flac-1.3.0pre3.tar.xz > flac-1.3.0pre3/include/share/compat.h:146:31: fatal error: share/win_utf8_io.h: No

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.03.2013 20:35, Janne Hyvärinen wrote: > > On 19.3.2013 15:49, JonY wrote: >> On 3/19/2013 19:59, Janne Hyvärinen wrote: >>> On 18.3.2013 12:25, Erik de Castro Lopo wrote: JonY wrote: > Before anyone does anything, see __wgetmainar

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.03.2013 13:35, JonY wrote: > Before anyone does anything, see __wgetmainargs > . > > It can expand wildcards. Since it already provides argc/argv/env, > it is more a less a drop-in replacem

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.03.2013 02:37, Erik de Castro Lopo wrote: > JonY wrote: >> On 3/17/2013 23:01, LRN wrote: >>>> All those ifdefs will at least be confined rather than spread >>>> out through the code. >>> I did it plib

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.03.2013 02:10, JonY wrote: > On 3/17/2013 23:01, LRN wrote: >>> All those ifdefs will at least be confined rather than spread >>> out through the code. >> I did it plibc-style: >> >> in comp

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.03.2013 18:55, JonY wrote: > On 3/17/2013 18:37, Erik de Castro Lopo wrote: >> JonY wrote: >> >>> On 3/17/2013 10:33, Janne Hyvärinen wrote: Here's a patch that makes MSVC compiled flac.exe able to use wildcards and encode/decode files

Re: [flac-dev] Patch to add Unicode filename support for win32 flac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.03.2013 06:33, Janne Hyvärinen wrote: > Here's a patch that makes MSVC compiled flac.exe able to use > wildcards and encode/decode files with Unicode characters in names. > It may not be the prettiest code but it fulfills its primary > purpose. I

Re: [flac-dev] flac-dev Digest, Vol 100, Issue 36

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2013 12:09, Erik de Castro Lopo wrote: > Marcus Johnson wrote: >> but no matter what you choose to do FLAC MUST REMAIN LOSSLESS. > > That has always been and will remain goal #1 for FLAC. FLAC stands for Free Lossless Audio Codec, so "lossy F

Re: [flac-dev] flac 1.3.0pre2 pre-release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09.03.2013 15:37, Erik de Castro Lopo wrote: > Hi all, > > Second and hopefully final pre-release is here: > > http://downloads.xiph.org/releases/flac/beta/ > src/libFLAC/metadata_iterators.c:442:4: warning: implicit declaration of function 'ftel

Re: [flac-dev] Answering the Hydrogen Audio thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.03.2013 20:39, Ben Allison wrote: > I would be willing to add Windows Unicode support (and large file > mode) to the flac binary tool, but frankly I'm not sure that it > could be done as a single cross-platform source file. There would > be a

Re: [flac-dev] Answering the Hydrogen Audio thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06.03.2013 01:20, Ben Allison wrote: > On 06.03.2013 01:02, Chris Moeller wrote: >> On Tue, 5 Mar 2013 11:39:19 -0500, Ben Allison wrote: >>> On 05.03.2013 12:30, Erik de Castro Lopo wrote: ktf said: > No unicode support for Windows either.

Re: [flac-dev] Fwd: flac 1.3.0pre1 prelease

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.03.2013 10:32, Erik de Castro Lopo wrote: > Andy Hawkins wrote: > >> Hi, >> >> In article >> <20130304070023.141c9f101622a34c46d68...@mega-nerd.com>, Erik de >> Castro Lopo wrote: project tends to be a pain unless one of the principal

Re: [flac-dev] flac 1.3.0pre1 prelease

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.03.2013 03:22, Erik de Castro Lopo wrote: > What I'm after now is testing of this source tarball on as many > systems as possible. W32 (mingw.org + MSys) - builds correctly. All tests passed. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11

Re: [flac-dev] [Flac-dev] Git branch with compiling fixes for win32

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.05.2012 17:11, Miroslav Lichvar wrote: > On Fri, May 04, 2012 at 11:22:00AM -0400, Cristian Rodríguez > wrote: >> El 03/05/12 12:19, Miroslav Lichvar escribió: >> >> >>> It makes the C function faster than the corresponding asm >>> routine, so

Re: [flac-dev] [PATCH 3/3] export MALLOC_PERTURB_ and MALLOC_CHECK_ in test suite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.04.2012 16:08, Erik de Castro Lopo wrote: > Cristian Rodríguez wrote: > >> That enables an special implementation that checks for common >> memory errors and will save us from a lot pain. --- >> test/test_bins.sh |2 ++ test/test_flac.s

Re: [flac-dev] Testing needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.02.2012 10:58, Erik de Castro Lopo wrote: > LRN wrote: > >> f:/src/mingw-flac/flac-1.2.2-rc1/src/share/utf8/iconvert.c:175:5: >> >> warning: passing argument 2 of 'libiconv' from incompatible pointer >>

Re: [flac-dev] Testing needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26.02.2012 14:18, Erik de Castro Lopo wrote: > I ... would appreciate reports of successful compiles (and even > more importantly any failures) on ... Windows ... > 1) I have to update automake version from 1.7 to 1.11. This might be fixable with

Re: [flac-dev] [PATCH] Remove even more CPP hackery

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09.02.2012 21:41, Ben Allison wrote: >>> Dave Yeo wrote: Yes that makes sense. Requiring a C99 compliant compiler seems quite >> reasonable. >>> Well I'm actually going to be even more reasonable than that. >>> The only >> bits of C99 that

Re: [flac-dev] Meet the new maintainer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06.02.2012 18:52, Olav Sunde wrote: > At 14:16 06.02.2012, you wrote: > >> Olav, >> >> A change like this could easily break the format. That would be >> a bad choice. > > That makes sense. Explains why it is not there today. > > >> On the oth

Re: [flac-dev] Gapless Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.02.2012 1:11, Declan Kelly wrote: > Many people who use FLAC to archive entire CDs (as opposed to > "albums" of tracks that may or may not be on the same CD) will rip > the entire disc and store it in a single FLAC file, with the CUE > sheet eit

Re: [flac-dev] Gapless Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.01.2012 12:44, Richard Schülein wrote: > Hi, > > > > i’m not part of the FLAC project, but i have a question regarding > FLAC and Gapless support… I hope, I get an answer from some of you > ;-) > > We are currently try to add Gapless support

Re: [flac-dev] [Flac-dev] Git branch with compiling fixes for win32

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.02.2012 14:52, Erik de Castro Lopo wrote: > In C99, the correct way to print a uint64_t value is: > Is it wise to aim at C99? While i have absolutely nothing against it, it is a known fact that MS never got around to support C99 in MSVC to any

Re: [Flac-dev] Compiling static libFLAC.a still requires libogg.dylib

On 17.08.2010 7:20, Glenn McCord wrote: > On Tue, Aug 17, 2010 at 3:12 PM, Paul Davis > wrote: >> On Mon, Aug 16, 2010 at 11:09 PM, Glenn McCord >> wrote: >> >>> libtool: link: gcc -I/Users/glennm/libOGG-i386/include -O3 >>> -funroll-loops -finline-functions -Wall -W -Winline -arch i386 -arch

Re: [Flac-dev] FLAC C API / Visual Studio 2008 FILE* Issue

On 06.01.2010 2:03, Ivailo Karamanolev wrote: > I managed to get around it. I used the stream functions and provided my own > callbacks for reading and writing. What's strange is that what I've done is > just copied the contents of read/write/seek/tell/eof callbacks from the > sources to my applica

[Flac-dev] Strange autotools check order in autogen.sh

for am in automake-$AM_NEEDED automake$AM_NEEDED \ automake automake-1.7 automake-1.8 automake-1.9 automake-1.10; do This code makes it check for automake-1.7 (AM_NEEDED evaluates to 1.7), then automake (unversioned wrapper), then 1.7 (again), 1.8, 1.9 and then 1.10 1) Why the check is g

Re: [Flac-dev] libFLAC header checking

On 06.11.2008 22:16, LRN wrote: > In stream_decoder.c function find_metadata_() checks whether a file is > valid or not. There are 4 cases it recognizes: > 1) file begins with 'fLaC' > 2) file begins with ID3 (skipped), followed by 'fLaC' > 3) file may begin w

[Flac-dev] libFLAC header checking

In stream_decoder.c function find_metadata_() checks whether a file is valid or not. There are 4 cases it recognizes: 1) file begins with 'fLaC' 2) file begins with ID3 (skipped), followed by 'fLaC' 3) file may begin with 10?? sync code (or 10, depends on endianess i supp