[flac-dev] How to change the dynamic library project name ogg to libogg?

Martijn van Beurden mvanb1 at gmail.com
Tue Jun 6 19:44:12 UTC 2023

Yes, I've tried that, and libogg.dll and libogg.obj get produced, but I
also het a linker warning that libogg.exp contains an out directive that is
not consistent, as it points to ogg.dll. So, the files get renamed, but the
'pointer' stays the same. Seems like a bug in either Visual Studio or
CMake, but I can't seem to find about it on Google.

Op di 6 jun. 2023 21:39 schreef LRN <lrn1986 at gmail.com>:

> On 06.06.2023 22:33, Martijn van Beurden wrote:
> > Hi,
> >
> > This rabbit hole went quite a bit deeper than I expected. Apparently,
> > CMake prepends 'lib' to library names for unix like environments
> > (including MinGW) but not for Visual Studio. So, when building on
> > Windows, you get either libFLAC.dll and libogg.dll or FLAC.dll and
> > ogg.dll depending on what toolchain you're using. I'm not quite sure
> > whether this makes sense. I've tried quite a few ways to override this
> > behaviour, but the most obvious solutions didn't work.
> >
> > Sorry, I've been trying various things for two hours today, I give up.
> > Perhaps someone else on this list knows the answer.
> >
> set_target_properties(foobar PROPERTIES
>   OUTPUT_NAME foobar
> Something like that. This should produce libfoobar-X, where X is the
> --
> O< ascii ribbon - stop html email! - www.asciiribbon.org
> _______________________________________________
> flac-dev mailing list
> flac-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/flac-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/flac-dev/attachments/20230606/730e739b/attachment.htm>

More information about the flac-dev mailing list