Displaying 20 results from an estimated 3000 matches similar to: "Lets work towards a new version"
2014 Jun 19
5
Lets work towards a new version
lvqcl wrote:
> 1)
> Current MSVC solution (FLAC.sln and numerous .vcproj files) was made with
> VC2005 Express and doesn't allow to build 64-bit files/libraries.
>
> IMHO it's time to add 64-bit support for MSVC builds, but AFAIK only Visual Studio
> 2012/2013 Express are free and allow to build 64-bit files.
>
> VS 2005/2008 use .vcproj files, and VS
2014 Jun 19
0
Lets work towards a new version
Erik de Castro Lopo wrote:
> It sees that the most serious bug in the flac bug tracker:
>
> https://sourceforge.net/p/flac/bugs/413/
>
> has been fixed in git. This fix alone is worth a new release so its
> time to work towards one.
>
> Things I need to do for this new release:
>
> * Deal with all current patches on the mailing list.
> * Review all bugs
2014 Jun 19
2
Lets work towards a new version
On Thu, 19 Jun 2014 05:00:39 +0400
lvqcl <lvqcl.mail at gmail.com> wrote:
>Erik de Castro Lopo wrote:
>
>> It sees that the most serious bug in the flac bug tracker:
>>
>> https://sourceforge.net/p/flac/bugs/413/
>>
>> has been fixed in git. This fix alone is worth a new release so its
>> time to work towards one.
>>
>> Things I need
2014 Jun 19
4
Lets work towards a new version
lvqcl wrote:
> Audacity still uses VS2008 and slowly tries to migrate to VS2012.
> But as stated at <http://wiki.audacityteam.org/wiki/Developing_On_Windows>,
> "Audacity is currently a 32-bit only application". So it doesn't need
> 64-bit builds.
> Currently its trunk contains 'audacity.sln' made with Visual C++ Express 2008
> and
2014 Jun 19
0
Lets work towards a new version
Erik de Castro Lopo wrote:
>> VS 2005/2008 use .vcproj files, and VS 2010/2012/2013 use .vcxproj
>> and .vcxproj.filters files, so it's possible to have two sets of
>> MSVS solution files: one for 2005/2008 and another for 2010/2012/2013.
>>
>> But there will be two .sln files: current FLAC.sln and new FLAC-vs2013.sln
>> (or FLAC-vs201x.sln? or is it better
2013 Aug 16
3
PATCH for MSVC++ 2005 Express
Recently I downloaded MSVC++2005 Express Edition and it turns out that it wasn't possible to compile all files without several changes:
1) FLAC.sln has one extra "EndProject" line
--- a\FLAC.sln 2013-06-17 11:57:09.000000000 +0400
+++ b\FLAC.sln 2013-08-16 20:19:34.630486700 +0400
@@ -157,7 +157,6 @@
EndProject
Project("{4cefbc7c-c215-11db-8314-0800200c9a66}") =
2019 Jul 14
8
Prelease now available
Hi all,
I have a new pre-reelase (with a GPG signature) up here:
http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz
http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz.asc
This code is built from commit 10a28d482a8e48b806f61ab766992b2add98ec43
plus another commmit to change the version numbers which I will
not be pushing to the public repo before the final release.
Note that audio files encoded
2008 May 13
2
[LLVMdev] patch for building llvm on Windows with MSVC 2008
These are the updated .sln and .vcproj files for building llvm with MSVC
2008.
It turned out that the compiling errors were because these projects wasn't
updated to reflect the actual status of the llvm files.
I checked all the files (removed, moved or added) and now they are ok.
It compiles all targets from the first "Build Solution", both for Debug and
for Release mode. You need
2019 Jul 14
1
Prelease now available
Janne Hyvärinen wrote:
> Minor changes needed for Visual Studio as the version is defined in the
> project files.
>
> Replace 'PACKAGE_VERSION=\"1.3.2\"' with
> 'PACKAGE_VERSION=\"1.3.3rc1\"' in
> src/libFLAC/libFLAC_dynamic.vcproj and libFLAC_static.vcproj. And
> replace 'PACKAGE_VERSION="1.3.2"' with
2014 Jul 04
0
[PATCH 1/3] removing asm version of precompute_partition_info_sums
Erik de Castro Lopo wrote:
>> 3)
>> Currently there are two ia32 asm files (bitreader_asm.nasm and stream_encoder_asm.nasm)
>> that are unused and not necessary to compile libFLAC: they offer no speed benefit
>> and the corresponding functions were commented out (*after* the release of 1.3.0):
>>
>>
2018 May 16
2
Windows build strangeness
I have the git monorepo, and Visual Studio 2015. I am finding that
running a build from the command line with msbuild (as a nightly job)
invariably fails on the first try, and succeeds on a retry.
The first msbuild command looks like this:
msbuild ALL_BUILD.vcxproj /p:Configuration="RelWithDebInfo" /m:6 /t:Rebuild
This appears to compile everything okay, but invariably fails with
2018 May 16
1
Windows build strangeness
What kind of missing symbols are you getting?
I had to work around dependencies for a Mingw32 build. See
https://reviews.llvm.org/D44650
On Wed, May 16, 2018, 13:13 via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> I have the git monorepo, and Visual Studio 2015. I am finding that
> running a build from the command line with msbuild (as a nightly job)
> invariably fails on the
2007 Nov 28
3
[PATCH] Add Visual Studio 2008 Prject files
I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are gone now).
The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for
2008 May 13
0
[LLVMdev] patch for building llvm on Windows with MSVC 2008
On Tue, 13 May 2008, Razvan Aciu wrote:
> These are the updated .sln and .vcproj files for building llvm with MSVC
> 2008.
> It turned out that the compiling errors were because these projects wasn't
> updated to reflect the actual status of the llvm files.
> I checked all the files (removed, moved or added) and now they are ok.
> It compiles all targets from the first
2010 Oct 12
2
libsrtp package anywhere?
Hi list,
I'm trying to create an asterisk 1.8 rpm with SRTP.
I found mention of a libsrtp rpm,
<http://qutecom.ipex.cz/RPMS/srtp-1.4.4-1.i386.rpm >
in these instructions,
<http://www.voip-info.org/wiki/view/Asterisk+SRTP>
but it is unreachable (by me, anyway).
The libSRTP source is here,
<http://srtp.sourceforge.net/download.html>.
Has this already been packaged for
2008 Feb 18
3
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
>There's a config.h file in the win32 subdirectory that implies that
it's
>supposed to be concatenated as part of the build process, but it
doesn't
>seem like that's happening from within the .sln script--am I missing a
>pre-build step someplace?
When config.h.in is hit in the build of configure the configure project,
the configure.h file from the win32 directory is
2008 May 12
0
[LLVMdev] building llvm on Windows
On May 11, 2008, at 12:59 PM, Razvan Aciu wrote:
> I tried to compile on Windows ( using the win32/llvm.sln in MSVC
> Express
> 2008 ) the new 2.3 branch and here are the results:
It would be great to get any windows improvements into the 2.3 release
if possible.
> 1. I needed to copy the file Configure.exe.embed.manifest to
> Configure.exe.intermediate.manifest . This is a
2018 May 16
2
Windows build strangeness
I think MSBuild isn't capable of re-running cmake and then reloading the
project files when CMakeLists.txt changes. It re-runs cmake, but then
continues the build with the stale projects. That probably explains the
"PipSqueek.cxx doesn't exist" errors. As for the link error, it could also
be caused by things like a file rename not getting picked up by MSBuild.
The fix is
2008 May 14
2
[LLVMdev] patch for building llvm on Windows with MSVC 2008
I verified the patch and it compiles all the targets, both in Debug and
Release modes.
If there is no someone else to keep the MSVC projects files updated, I will
try from time to time to update them and to add the new targets.
Maybe a note must be put in "docs/GettingStartedVS.html" at the Requirements
section that llvm needs now MSVC (Express) 2008 to compile.
Razvan
-----
2016 Jan 22
2
Lets do a 1.3.2 release
lvqcl wrote:
> Then IMHO all three build systems (configure && make, Makefile.lite
> and MSVC) should be synchronized with each other
+1
> TO ERIK:
>
> I have some patches, but they either modify MSVC .vcxproj files,
> or win_utf8_io.c/.h, so they conflict with patches from Evan Ramos.
> So should they be applied? rejected? postponed until after flac 1.3.2?
We