Re: [flac-dev] MSVS: debug flac.exe uses release libogg_static.lib
Ralph Giles wrote: The way we've been doing the Opus stuff is to have the project files expect a build in a parallel checkout. so: c:\dev\flac\FLAC.sln expects to find an ogg build in c:\dev\ogg\win32\VS2010\ Not as obvious as having a monolithic build, but it seems to work once you've figured it out. And each arch and target can reference the corresponding target in the dependency. Good idea, but... there are 5 folders in libogg/win32: VS6, VS2003, VS2005, VS2008 and VS2010. And FLAC provides solution/project files for MSVS 2005. Should FLAC project files refer to libogg/win32/VS2005? But I suspect that developers use mostly newer versions (2008/2010/2012). ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] MSVS: debug flac.exe uses release libogg_static.lib
Janne Hyvärinen wrote: The project files aren't compatible with FLAC by default anyway as they default dynamic linking to runtimes. Either one needs to bundle own project files that assume certain directory structure or some other way needs to be thought of. One option that would not require extra work from the user is to bundle the ogg sources. Bundling the source code of another project in the FLAC sources is always a bad idea. The way I would fix this on Linux would be to have a script that grabs the Ogg sources and untars them in a know location before building. Unfortunately my limited experience with windows suggests this kind of thing is difficult on that platform. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] MSVS: debug flac.exe uses release libogg_static.lib
On 2013-09-30 4:53 PM, Erik de Castro Lopo wrote: I'd be keen to have the windows build automatically do the sanest possible thing, preferably with anyone having to copy files. The way we've been doing the Opus stuff is to have the project files expect a build in a parallel checkout. so: c:\dev\flac\FLAC.sln expects to find an ogg build in c:\dev\ogg\win32\VS2010\ Not as obvious as having a monolithic build, but it seems to work once you've figured it out. And each arch and target can reference the corresponding target in the dependency. -r ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] MSVS: debug flac.exe uses release libogg_static.lib
On 2013-09-29 2:14 AM, lvqcl wrote: With current settings, MSVS links debug version of flac.exe (and other .exe and .dll files) with the release version of libogg_static.lib. MSVS issues a warning LNK4098: defaultlib 'libcmt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library What's the reason in this setting? Sounds like a bug. Debug targets should link to debug builds of their dependencies to simplify debugging. -r ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
