Displaying 5 results from an estimated 5 matches for "vs201x".
Did you mean:
vs2013
2014 Jun 19
5
Lets work towards a new version
....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 to rename FLAC.sln to FLAC-vs2005.sln?)
>
> What do you think?
I think having 64 bit builds on Windows would be a good thing. Unfortunately
since I don't have *any* Windows machines to even test on, zero recent
experience on Windows and little desire to reaquaint my...
2014 Jun 19
10
Lets work towards a new version
Hi all,
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 reported against 1.3.0 on the sf.net.
* Testing and coordination of testing
2014 Jun 19
0
Lets work towards a new version
...files.
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 to rename FLAC.sln to FLAC-vs2005.sln?)
What do you think?
2)
VC projects contain relative paths such as "..\..\include". Is it better to
leave them as is or to change to something like "$(SolutionDir)include"?
3)
Currently there are two ia32 asm files (...
2014 Jun 19
0
Lets work towards a new version
...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 to rename FLAC.sln to FLAC-vs2005.sln?)
>>
>> What do you think?
>
> I think having 64 bit builds on Windows would be a good thing. Unfortunately
> since I don't have *any* Windows machines to even test on, zero recent
> experience on Windows and lit...
2014 Jun 19
2
Lets work towards a new version
...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 to rename FLAC.sln to FLAC-vs2005.sln?)
>
>What do you think?
>
>
>2)
>VC projects contain relative paths such as "..\..\include". Is it better to
>leave them as is or to change to something like "$(SolutionDir)include"?
>
>3)
>...