Ralph Giles
2013-Oct-01 00:18 UTC
[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
lvqcl
2013-Oct-02 17:27 UTC
[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).
Janne Hyvärinen
2013-Oct-02 17:36 UTC
[flac-dev] MSVS: debug flac.exe uses release libogg_static.lib
On 2.10.2013 20:27, lvqcl wrote:> 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). >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.