Issue 110 in mp4v2: No Recent Windows Binaries Posted
mp...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 110 by CarlEd...@gmail.com: No Recent Windows Binaries Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
What steps will reproduce the problem?
1. I used to be able to build the current mp4v2 tool set on Windows using
the free Visual Studio Express available from Microsoft, with only some
minor complaints
2. Now, however, with the trunk pulled from subversion and the latest
Visual Studio Express (10? 2010? whatever was available last week), the
solution and projects files are not recognized at all any more.
3. For the minimal amount of C[punctuation marks] programming that I do (I
work mostly in Python and Haskell), I can't really justify buying the full
developer environment. So I am stuck with a way out of date toolset with
lots of bugs that reportedly are fixed in the current version.
What version of the product are you using? On what operating system?
mp4v2 pulled from subversion a few days ago, the current Visual Studio
Express, Windows 7 x64
Please provide any additional information below.
If somebody could build Windows 7-compatible (64-bit preferred) versions of
the tools and post them somewhere, I'd be eternally grateful. A new set
every couple months, or when there have been significant developments,
would be even better. Thanks!
mp...@googlecode.com
Comment #1 on issue 110 by CarlEd...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
And, yes, I know and acknowledge that if I could just switch to a decent
Un*x based system (e.g., Linux, Mac OS X), where the developer tools are
free, I would not have this problem. Having mostly hacked Un*x boxes for
over two decades, I remember the advantages. But these days, Windows is
unfortunately a necessity for a lot of my work.
mp...@googlecode.com
Owner: kid...@gmail.com
Comment #2 on issue 110 by kid...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
When you say "the solution and projects files are not recognized at all any
more," what do you mean? I would think that it'd try and open the VS2008
solution file and go through the conversion wizard. Could you be a bit
more specific about the issues you're running into?
In any event, I agree--we should have a VS2010 project. I'll work on
getting one up and running that works with the VS2010 express stuff as a
lowest common denominator before I do a release.
mp...@googlecode.com
Comment #3 on issue 110 by CarlEd...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
"Could you be a bit more specific about the issues you're running into?"
To reproduce the problem and give more detail, I just checked out revision
479 using svn. Then when I try to open the vstudio9.0/mp4v2.sln file, I'm
asked whether to open it with "Visual C++ Express 2010" or "Visual C++
Express 10", but the result is the same.
Just like when I previously successfully built mp4v2, the conversion Wizard
opens. The difference is that, selecting the default Wizard options as
before, now results in an error message "Some of the properties associated
with the solution could not be read." and a popup saying "One or more
projects in the solution were not loaded correctly."
The resulting solution in Visual Studio Express lists *all* project files
as unavailable and unloaded. There is no way to build anything. Under
previous versions, I seem to recall some warning message during conversion,
but in the end everything would build just fine.
mp...@googlecode.com
Comment #4 on issue 110 by kid...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
okay....tried out the express versions, and the issue is mp4v2 now has 64
bit builds in the windows projects. The express variants of visual studio
don't support 64 bit (way to go, MSFT...), which is what I think is causing
the failure. So I'll generate full binaries for r479 and post those in the
download section.
mp...@googlecode.com
Status: Completed
Comment #5 on issue 110 by kid...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
Okay, binaries should be posted here:
...I built both x86 and x64 builds, release and debug, of the r479
release. All the command line tools should be in there, along with
#include stuff and some other miscellaneous "stuff." I didn't build the
static libs, since I figure most people won't want to use those for
complying with the MPL.
Going to close this--reopen it if you have any issues. Thanks.
mp...@googlecode.com
Comment #6 on issue 110 by CarlEd...@gmail.com: No Recent Windows Binaries
Posted
http://code.google.com/p/mp4v2/issues/detail?id=110
Thank you so much, Kidjan! I (and all others who labor without proper
Windows development tools) are much obliged.