quoted from the website:

> Sets the base name of the output file; type and platform specific pre- and suffixes are added automatically
> - this setting does not support platform suffixes

I must be blind but I can't find the code that adds the 'lib' prefix on GitHub. I need to check something:

Is it correct to say that
- under Macosx and Linux, the 'lib' prefix is added if target is a library.
- under Windows, nothing is added and targetName is used as it.

Otherwise, if you have the link with the matching line highlihted on GH.

On Wednesday, 11 November 2015 at 05:03:47 UTC, BBaz wrote:
> quoted from the website:
>
>> Sets the base name of the output file; type and platform specific pre- and suffixes are added automatically
>> - this setting does not support platform suffixes
>
> I must be blind but I can't find the code that adds the 'lib' prefix on GitHub. I need to check something:
>
> Is it correct to say that
> - under Macosx and Linux, the 'lib' prefix is added if target is a library.
> - under Windows, nothing is added and targetName is used as it.
>
> Otherwise, if you have the link with the matching line highlihted on GH.

From what i understand yes. That option ( I think ) is for if you have a project foo with libraries bar and baz you can make it call the libs (lib)foobar.(a|so|dylib|lib |.etc) and libfoobaz.a