Closed GoogleCodeExporter closed 9 years ago
Reclassified as an enhancement...
Original comment by david.g.hoyt
on 17 Aug 2010 at 8:04
I can submit a patch.
The only thing I need is the rules about what to do with the twolame library -
where its place is in the OSSBuild directory tree.
Original comment by wl2776@gmail.com
on 18 Aug 2010 at 6:56
It needs to be built w/ our msys environment (Tools/init msys.bat) and added to
our build script (Libraries/Build-All-Windows-x86.sh). Please ensure that make
check passes on all tests it should pass for the platform.
Use the configuration options that you see other dependencies using so it'll
place the installed files in the proper place during the build phase. At the
end of the script (Build-All-Windows-x86.sh) we move them over into
Shared/Build/Windows/Win32/ and generate pkg-config and libtool templates for
use the first time someone attempts to build the dependent libraries from
scratch. Once the files are in the Shared/ directory they can be committed to
the repo.
Original comment by david.g.hoyt
on 18 Aug 2010 at 4:52
twolame isn't building correctly w/ msys/mingw. Building it via visual studio
places a dependency on the wrong C runtime. Until it gains better msys/mingw
support, it will have to be put on hold.
Original comment by david.g.hoyt
on 10 Sep 2010 at 5:23
Please create a new issue if you're able to get twolame built with
MSys/MinGW-w64 in the future.
Original comment by david.g.hoyt
on 14 Sep 2010 at 8:23
> Building it via visual studio places a dependency on the wrong C runtime.
If I understand, it will depend on the current CRT (MSVCRT). What's wrong with
it?
Original comment by wl2776@gmail.com
on 15 Sep 2010 at 8:24
Original issue reported on code.google.com by
wl2776@gmail.com
on 16 Aug 2010 at 11:21